Error handler: err.scriptline -1

[Simpel]

Hi.

I have an error handler that show as err.scriptline always -1 if compiled. Example:

Global $oMyError = ObjEvent("AutoIt.Error", "_ErrorHandler")
_Example()
Exit

Func _Example()
    Const $bAdoStateOpen = 1
    Local $oAdoConnection = ObjCreate("ADODB.Connection")
    $oAdoConnection.properties("Prompt") = 2
    Local $sQuery = "DRIVER={Oracle in Orahome11_32Bit};SERVER=xxx;DBQ=xxx.;UID=xxx;PWD=xxx;"
    If $oAdoConnection.state = $bAdoStateOpen Then $oAdoConnection.close
    $oAdoConnection.connectionstring = $sQuery
    $oAdoConnection.open ; ################################# This causes the error ################################
    If $oAdoConnection.state <> $bAdoStateOpen Then
        Return SetError(1)
    EndIf
EndFunc

Func _ErrorHandler()
    Local $HexNumber = Hex($oMyError.number,8)
    MsgBox(0,"Fehler","An error occured:" & @CRLF & _
        "err.description is: "    & @TAB & $oMyError.description    & @CRLF & _
        "err.windescription:"     & @TAB & $oMyError.windescription & @CRLF & _
        "err.number is: "         & @TAB & $HexNumber              & @CRLF & _
        "err.lastdllerror is: "   & @TAB & $oMyError.lastdllerror   & @CRLF & _
        "err.scriptline is: "     & @TAB & $oMyError.scriptline     & @CRLF & _
        "err.source is: "         & @TAB & $oMyError.source         & @CRLF & _
        "err.helpfile is: "       & @TAB & $oMyError.helpfile       & @CRLF & _
        "err.helpcontext is: "    & @TAB & $oMyError.helpcontext)
    Return SetError(1)
EndFunc

If I run this script from SciTE it shows err.scriptline: 12:

But if I compile err.scriptline is: -1:

How can I fix this?

Regards, Conrad

Edited May 30, 2019 by Simpel
typo

[Earthshine]

sorry, cannot read German to read that error. from your error number it looks like a Logon Failure

 

Edited June 6, 2018 by Earthshine

[mLipok]

@Simpel this is very similar question, and answer like this following:

 

EDIT:
err.scriptline -1 is because you are using compiled script, which will not return @ScriptLineNumber

 

Edited June 6, 2018 by mLipok

[Simpel]

Hi.

So @mLipok, by the way you probably solved the error behind that question. But that was not intended. That’s why I did post the german messages - only wanted to show the behavior with scriptline.

I was looking for an error handler telling me the scriptline even if compiled. Of course I have to deal with error handling in the code at every point there could something happen. But there will always be parts of code I do forget to check. So I don’t want to crash the script but catch the error messages including scriptline to solve that error later (I ask my users to make a screenshot). But if that kind of error handler can’t handle the scriptlines I had to disable this and better let crash my tool but with an message including a scriptline. Or is there another possibility?

Conrad

[mLipok]

27 minutes ago, Simpel said:

I was looking for an error handler telling me the scriptline even if compiled. Of course I have to deal with error handling in the code at every point there could something happen.

This following conceptual snippet:

#Au3Stripper_Parameters=/MO /RSLN

_Example()
Func _Example()
    _SomeFunction()
    If @error Then MsgBox($MB_ICONERROR, 'SomeFunction', '@error = ' & @error & @CRLF & '@extended = ' & @extende & @CRLF & '@ScriptLineNumber = ' & @ScriptLineNumber)
EndFunc

Func _SomeFunction()
    Return SetError(1)
EndFunc

is soultion to your problem - of course in outline, because it's just a sketch.

I'm using such kind of @error handling all the last 3..5 years, with quite good success. For this reason I rewrite few UDF (ADO, POP, XML, and few of my own) - to have better error handling + parameters validation.

 

 

[Simpel]

That kind of handler I use to catch errors in that part of scripts I write myself. But there are two things I can’t barely deal with. First are UDFs from others which I should understand but shouldn’t rewrite at all, I think. Probably I have to.

But more important and that’s the problem here are errors with objects. Errors with objects will definitely crash the script if not catch with an error handler function like above or am I wrong? Is there a possibility catching them and showing the err.scriptline? The crashing messages on object errors (if not having an error handler) are showing the correct error scriptline. So how can I do that by myself and not exiting/crashing the script?

Conrad

P.S. Anyway, on monday I will expand my “normal” error handling with /rsln for errors not dealing with object errors.

[mLipok]

1 hour ago, Simpel said:

But more important and that’s the problem here are errors with objects.

Check my ADO and XML UDF and focus on how I handle COM errors.

If COM errors is fired then I set and return specyfic @error and @extended

IMHO each other UDF using ActiveX Object  should report COM issues to @error and @extended in a similar way.

 

Edited June 7, 2018 by mLipok