Sign in to follow this  
Followers 0
Tjalve

Help troubleshooting by printing the row number?

7 posts in this topic

Hi. Im writing a script with alot of rows. The problem is that when i get an error it say row XXXX and thats alot more then i currently have in my script. I guess that when you compile the script adds all the include files and remove all the comments and stuff?

In that case its almost impossibel to find the error thats on row 1685. So my question. is there a way to print the row thats currently beeing executed? that way, i could print the row number on sereval places and then calculate where the error is.

Share this post


Link to post
Share on other sites



In Scite you can find under the "Tools" menu an option named "Trace: Add Trace Lines". this will print every line to the console when you run your script.

I think the error message also should tell you what file and line it refers to.

Share this post


Link to post
Share on other sites

If you using SciTE4AutoIt , then you can use this:

#AutoIt3Wrapper_Run_Au3Stripper=Y
#Au3Stripper_Parameters=/MO

Signature beginning:   Wondering who uses AutoIT and what it can be used for ?
* GHAPI UDF - modest begining - comunication with GitHub REST API *
ADO.au3 UDF     POP3.au3 UDF     XML.au3 UDF    How to use IE.au3  UDF with  AutoIt v3.3.14.x  for other useful stuff click the following button

Spoiler

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

My contribution (my own projects): * Debenu Quick PDF Library - UDF * Debenu PDF Viewer SDK - UDF * Acrobat Reader - ActiveX Viewer * UDF for PDFCreator v1.x.x * XZip - UDF * AppCompatFlags UDF * CrowdinAPI UDF * _WinMergeCompare2Files() * _JavaExceptionAdd() * _IsBeta() * Writing DPI Awareness App - workaround * _AutoIt_RequiredVersion() * Chilkatsoft.au3 UDF * TeamViewer.au3 UDF * JavaManagement UDF * VIES over SOAP * WinSCP UDF * GHAPI UDF - modest begining - comunication with GitHub REST API *

My contribution to others projects or UDF based on  others projects: * _sql.au3 UDF  * POP3.au3 UDF *  RTF Printer - UDF * XML.au3 - BETA * ADO.au3 UDF SMTP Mailer UDF *

Useful links: * Forum Rules * Forum etiquette *  Forum Information and FAQs * How to post code on the forum * AutoIt Online Documentation * AutoIt Online Beta Documentation * SciTE4AutoIt3 getting started * Convert text blocks to AutoIt code * Games made in Autoit * Programming related sites * Polish AutoIt Tutorial * DllCall Code Generator * 

Wiki: Expand your knowledge - AutoIt Wiki * Collection of User Defined Functions * How to use HelpFile * Best coding practices * 

IE Related:  * How to use IE.au3  UDF with  AutoIt v3.3.14.x * Why isn't Autoit able to click a Javascript Dialog? * Clicking javascript button with no ID * IE document >> save as MHT file * IETab Switcher (by LarsJ ) * HTML Entities * _IEquerySelectorAll() (by uncommon) * 

I encourage you to read: * Global Vars * Best Coding Practices * Please explain code used in Help file for several File functions * OOP-like approach in AutoIt * UDF-Spec Questions *  EXAMPLE: How To Catch ConsoleWrite() output to a file or to CMD *

"Homo sum; humani nil a me alienum puto" - Publius Terentius Afer
"Program are meant to be read by humans and only incidentally for computers and execute" - Donald Knuth, "The Art of Computer Programming"
:naughty:  :ranting:, be  :) and       \\//_.

Anticipating Errors :  "Any program that accepts data from a user must include code to validate that data before sending it to the data store. You cannot rely on the data store, ...., or even your programming language to notify you of problems. You must check every byte entered by your users, making sure that data is the correct type for its field and that required fields are not empty."

Signature last update: 2017-06-04

Share this post


Link to post
Share on other sites

While I'm here, I should add that I use this..

;
; debug()
;
; provides quick debug report in your console..
;
; if your text editor can do it (probably), this is a great
; way to get debug output without halting the script execution..
;
; NOTE: if you call debug() in a compiled script, and $c-debug is set to $ON,
; you will get the debug() output dump()ed, instead.
;
func debug($d_string, $ln=false)
    if @compiled then
        if $ce_debug = $ON then return dump($d_string, "compiled", "debug")
        return 0
    endif
    local $pre
    if $ln then $pre = ".\" & @ScriptName & "(" & $ln & ") : ==> "
    ConsoleWrite($pre & $d_string & $LOG_LF)
endfunc

a LOT. Feed it something like..

debug("some_variable =>" & $some_variable & "<=", @ScriptLineNumber);debug

And get an instant read-out of whatever it is you are trying to track (in my IDE, I can click on the output line in the console to go straight to the offending line.).

By the way, the "sister" function, dump() goes like this..

;
; dump()
;
; like debug(), but to a file..
;
func dump($d_string, $ln=false, $dump_file="dump")
    if @compiled and ($ce_debug = 0 or $ce_debug = $OFF) then return 0
    local $pre
    if $ln then $pre = ".\" & @ScriptName & " (" & $ln & ") : ==> "
    FileWriteLine($dump_file, $pre & $d_string & $LOG_LF)
endfunc

I usually have a preference in the app's ini file for $ce_debug, to enable debugging in the compiled version, or not, as required.

Aslo, why not simply run the script from inside your IDE? It's a lot easier to track down bugs than with a compiled .exe.

;o) Cor


nothing is foolproof to the sufficiently talented fool..

Share this post


Link to post
Share on other sites

Thanx for the input so far guys. I will test your sugestions.

Of course i debug the script in the editor (and then i get the excat row) but the system wehre i run the script is abit diffrent from where i compile it. Therefor there are often problems surfacing when i run the compiled version and i need a simpel way to find the error without the help of the editor.

Share this post


Link to post
Share on other sites

An easy solution could be to systematically embed your source code in the compiled script, and fileinstall it when running in debug mode :

If @compiled AND $CmdLine[ $CmdLine[0] ] = "/debug" Then FileInstall(@ScriptFullPath, @TempDir & "\" & StringRegExpReplace(@ScriptFullPath, ".*\\(.*)\..*", "$1.au3"), 1)

Now if you run yourCompiled.exe /debug , the source file yourCompiled.au3 while be extracted in %temp%.

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