Sign in to follow this  
Followers 0
rofl0r

Please fix Line -1 bug

6 posts in this topic

every error happens on line -1. that is so annoying.

since the scripts cannot be debugged, at least knowing the right line number would help a lot.

Share this post


Link to post
Share on other sites



rofl0r,

I take it you are running this script as a compiled .exe - compiling removes the line number information so you always get the generic "-1" error. Just run the source code from SciTE and then the line number giving the error will become apparent.

You do have the source code, I presume? :)

M23


Any of my own code posted anywhere on the forum is available for use by others without any restriction of any kind._______My UDFs:

Spoiler

ArrayMultiColSort ---- Sort arrays on multiple columns
ChooseFileFolder ---- Single and multiple selections from specified path treeview listing
Date_Time_Convert -- Easily convert date/time formats, including the language used
ExtMsgBox --------- A highly customisable replacement for MsgBox
GUIExtender -------- Extend and retract multiple sections within a GUI
GUIFrame ---------- Subdivide GUIs into many adjustable frames
GUIListViewEx ------- Insert, delete, move, drag, sort, edit and colour ListView items
GUITreeViewEx ------ Check/clear parent and child checkboxes in a TreeView
Marquee ----------- Scrolling tickertape GUIs
NoFocusLines ------- Remove the dotted focus lines from buttons, sliders, radios and checkboxes
Notify ------------- Small notifications on the edge of the display
Scrollbars ----------Automatically sized scrollbars with a single command
StringSize ---------- Automatically size controls to fit text
Toast -------------- Small GUIs which pop out of the notification area

 

Share this post


Link to post
Share on other sites

every error happens on line -1. that is so annoying.

since the scripts cannot be debugged, at least knowing the right line number would help a lot.

Welcome to the AutoIt forums rofl0r :)

Adding the line number to compiled scripts won't happen because of the bloat this would require.

You can run the script from SciTE and then errors with line numbers are reported. There are also debugging features in SciTE to add and remove extra debugging code. Stumpii has a debugger script in Example Scripts.

Even better, write the script so that errors are either prevented or handled in some helpful way. For example, check that you do not exceed the range of an array with IsArray and with UBound, check the return from functions, and @error and @extended.


Serial port communications UDF Includes functions for binary transmission and reception.printing UDF Useful for graphs, forms, labels, reports etc.Add User Call Tips to SciTE for functions in UDFs not included with AutoIt and for your own scripts.Functions with parameters in OnEvent mode and for Hot Keys One function replaces GuiSetOnEvent, GuiCtrlSetOnEvent and HotKeySet.UDF IsConnected2 for notification of status of connected state of many urls or IPs, without slowing the script.

Share this post


Link to post
Share on other sites

Welcome to the AutoIt forums rofl0r :)

Adding the line number to compiled scripts won't happen because of the bloat this would require.

You can run the script from SciTE and then errors with line numbers are reported. There are also debugging features in SciTE to add and remove extra debugging code. Stumpii has a debugger script in Example Scripts.

Even better, write the script so that errors are either prevented or handled in some helpful way. For example, check that you do not exceed the range of an array with IsArray and with UBound, check the return from functions, and @error and @extended.

the error that just happened was a missing $ sign before a variable name.

things like this happen all the time if you're coding in different languages.

the error displayed was "error parsing function call line -1".

since we use kinda framework here which launches the exe with the right parameters, i cannot debug the script directly.

i doubt that saving the line number information would be that much of an overhead.

the second error was a missing "\programs" when trying to create a shortcut like this $lnk = @StartMenuCommonDir & "\Utilities\blah.lnk"...

both together took 2,5h to debug, since i had to reboot the target machine every time to test every little code change

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0