aisc Posted December 26, 2009 Share Posted December 26, 2009 I have a long running script, which occasionally errors. The compiled mode shows the error as line -1. When I run in debug, I never seem to find the error; even when running it for a long time. Is there any of the compile options that allow the runtime to report the line that the error occured on? I tried the include scriptsource option, but reading the forum, it doesn't appear that is what the option is for. L'il help? Thanks, aisc Link to comment Share on other sites More sharing options...
darkjohn20 Posted December 26, 2009 Share Posted December 26, 2009 How can you expect help without showing us the script? There are infinite possibilities of what could be wrong, we can't just guess... Link to comment Share on other sites More sharing options...
picaxe Posted December 26, 2009 Share Posted December 26, 2009 Try creating a log file by adding some FileWrite statements in your code, to finding out where it may be failing when compiled. As per darkjohn20 you will need to provide more info. Link to comment Share on other sites More sharing options...
aisc Posted December 26, 2009 Author Share Posted December 26, 2009 The code is a thousand lines, so I'm not sure where it's dying exactly. My question was just whether there was a way to get the run time to spit out a line number, rather than line -1. I do like the FileWrite idea. I have a lot of consolewrites... I could replace those. Thanks! aisc Link to comment Share on other sites More sharing options...
Yashied Posted December 26, 2009 Share Posted December 26, 2009 Run your script in SciTE... My UDFs: iKey | FTP Uploader | Battery Checker | Boot Manager | Font Viewer | UDF Keyword Manager | Run Dialog Replacement | USBProtect | 3D Axis | Calculator | Sleep | iSwitcher | TM | NetHelper | File Types Manager | Control Viewer | SynFolders | DLL Helper Animated Tray Icons UDF Library | Hotkeys UDF Library | Hotkeys Input Control UDF Library | Caret Shape UDF Library | Context Help UDF Library | Most Recently Used List UDF Library | Icons UDF Library | FTP UDF Library | Script Communications UDF Library | Color Chooser UDF Library | Color Picker Control UDF Library | IPHelper (Vista/7) UDF Library | WinAPI Extended UDF Library | WinAPIVhd UDF Library | Icon Chooser UDF Library | Copy UDF Library | Restart UDF Library | Event Log UDF Library | NotifyBox UDF Library | Pop-up Windows UDF Library | TVExplorer UDF Library | GuiHotKey UDF Library | GuiSysLink UDF Library | Package UDF Library | Skin UDF Library | AITray UDF Library | RDC UDF Library Appropriate path | Button text color | Gaussian random numbers | Header's styles (Vista/7) | ICON resource enumeration | Menu & INI | Tabbed string size | Tab's skin | Pop-up circular menu | Progress Bar without animation (Vista/7) | Registry export | Registry path jumping | Unique hardware ID | Windows alignment More... Link to comment Share on other sites More sharing options...
slayerz Posted December 26, 2009 Share Posted December 26, 2009 Yup, run it in scite and try to repeat what you do to reproduce the error... Scite is really helpful in debugging script like that AUTOIT[sup] I'm lovin' it![/sup] Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now