Catching COM errors when assigning a value to chained Object

[donnyh13]

Good day AutoIt community!

Before clogging Trac with another ticket, I thought I would ask the following here:

Is it considered normal behaviour that a COM error handler cannot catch COM Errors when assigning values to an invalid chained COM Object? e.g.:

Global $oCOM_ErrorHandler = ObjEvent("AutoIt.Error", _ComErrorHandler)

Global $oFake = $oCOM_ErrorHandler

$oFake.Fake1.Fake2 = 1

Func _ComErrorHandler(ByRef $oError)
    ConsoleWrite("! We intercepted a COM Error" & @CRLF)
EndFunc

Quote

"C:\AutoIt Scripts\Testings.au3" (32) : ==> Variable must be of type "Object".:
$oFake.Fake1.Fake2 = 1
$oFake.Fake1^ ERROR

I know I can split the chain, but I was just wondering.

Thank you, and Best regards,

Donny

Edit: AutoIt version 3.3.18.0

Edited 7 hours ago by donnyh13

[mLipok]

Which AutoIt version ?

[donnyh13]

Right, sorry.

3.3.18.0.

Thank you.

[mLipok]

2 hours ago, donnyh13 said:

Right, sorry.

3.3.18.0.

Thank you.

I'm little confused.
Do you mean that this issue occurs on Au3.3.18.0 ?

Edited 5 hours ago by mLipok

[mLipok]

Take a look here:
https://www.autoitscript.com/trac/autoit/ticket/3167

I think this was fixed in 2021 > 3.3.16.0 (March 06, 2022) (Release)

I even tested the example in ticket #3167 and modified them by adding report from 3.3.18.0

 

[donnyh13]

16 minutes ago, mLipok said:

I'm little confused.
Do you mean that this issue occurs on Au3.3.18.0 ?

Yes, for me anyway. Does my example not crash for you?

6 minutes ago, mLipok said:

Take a look here:

I tried both examples and they all work for me.
But  notice you aren't trying to assign a value in those examples, only call a method/retrieve a property. Whereas in mine, it is attempting to assign a value to Fake2.

Edited 5 hours ago by donnyh13

[donnyh13]

Running this modified script produces:

Global $oCOM_ErrorHandler = ObjEvent("AutoIt.Error", _ComErrorHandler)

Global $oFake = $oCOM_ErrorHandler

$oFake.Fake1 = 1
$oFake.Fake1.Fake2 = 1

Func _ComErrorHandler(ByRef $oError)
    ConsoleWrite("! We intercepted a COM Error" & @CRLF)
EndFunc

Quote

! We intercepted a COM Error
! We intercepted a COM Error
"C:\Users\Owner\Desktop\New AutoIt v3 Script.au3" (6) : ==> Variable must be of type "Object".:
$oFake.Fake1.Fake2 = 1
$oFake.Fake1^ ERROR

 

[mLipok]

10 minutes ago, donnyh13 said:

But  notice you aren't trying to assign a value in those examples, only call a method/retrieve a property. Whereas in mine, it is attempting to assign a value to Fake2.

this

; Initialize COM error handler
$oErrorHandler = ObjEvent("AutoIt.Error", _ErrFunc)
Func _ErrFunc($oError)
    ConsoleWrite("!ERROR caught" & @CRLF)
EndFunc

; Create shell object
$oObj = ObjCreate("shell.application")

;The following line should trigger COM error handler (at the last dot).
$oObj.Windows().Item(666).bzzzzzzz = 2

still works.

checking yours.

[mLipok]

so I modify yours example:

Global $oCOM_ErrorHandler = ObjEvent("AutoIt.Error", _ComErrorHandler)

Global $oFake[]

$oFake.Fake1 = 1
$oFake.Fake1.Fake2 = 1

Func _ComErrorHandler(ByRef $oError)
    #forceref $oError
    ConsoleWrite("! We intercepted a COM Error" & @CRLF)
EndFunc   ;==>_ComErrorHandler

and yes you caught a malicious imp

Please feel free to open ticket: https://www.autoitscript.com/trac/autoit

[mLipok]

here you have better example:

Global $oCOM_ErrorHandler = ObjEvent("AutoIt.Error", _ComErrorHandler)

Global $oFake[]
Global $oTestObject[]

$oFake.TestObject = $oTestObject
$oFake.TestObject.Check1 = 1

$oFake.FakeObject = 1
$oFake.FakeObject.Check2 = 1

Func _ComErrorHandler(ByRef $oError)
    #forceref $oError
    ConsoleWrite("! We intercepted a COM Error" & @CRLF)
EndFunc   ;==>_ComErrorHandler

 

Edited 4 hours ago by mLipok

[donnyh13]

Thank you for looking into it @mLipok, and for the example. I'll go post a ticket then.

[mLipok]

Do you want to open a ticket yourself or should I do it for you?

[mLipok]

1 minute ago, donnyh13 said:

Thank you for looking into it @mLipok, and for the example. I'll go post a ticket then.

You're welcome

and
Ok

Edited 4 hours ago by mLipok

[donnyh13]

3 minutes ago, mLipok said:

Do you want to open a ticket yourself or should I do it for you?

Given you have better knowledge on terminology, you can do it if you have time. But I know you are busy. So if not, I can.

[mLipok]

21 minutes ago, donnyh13 said:

you can do it if you have time

https://www.autoitscript.com/trac/autoit/ticket/4083

[donnyh13]

Thanks, I appreciate it.

[donnyh13]

@mLipok, I noticed the error handler isn't getting called in the other error scenarios (No ConsoleWrites), but the crash is still being produced. Is it because we are technically using maps in these new examples? Whereas in my original example I was using the COM error handler Object as a base Object?

Edited 3 hours ago by donnyh13

[mLipok]

Did you check my modified code from the ticket?
 

Global $oCOM_ErrorHandler = ObjEvent("AutoIt.Error", _ComErrorHandler)

Global $oFake[]
Global $oTestObject[]

$oFake.TestObject = $oTestObject
$oFake.TestObject.Check1 = 1

$oFake.FakeObject = 1

ConsoleWrite($oFake.FakeObject.Check2 & @CRLF) ; _ComErrorHandler() is not fired even this was already fixed in https://www.autoitscript.com/trac/autoit/ticket/3167

$oFake.FakeObject.Check3 = 1 ; _ComErrorHandler() is not fired and AutoIt ends with "Variable must be of type "Object""

Func _ComErrorHandler(ByRef $oError)
        #forceref $oError
        ConsoleWrite("! We intercepted a COM Error" & @CRLF)
EndFunc   ;==>_ComErrorHandler

# both .Check2 and .Check3 should fires _ComErrorHandler() and show the console message

 

[mLipok]

just changed the example a little:

Global $oCOM_ErrorHandler = ObjEvent("AutoIt.Error", _ComErrorHandler)

Global $oFake[]
Global $oTestObject[]

$oFake.TestObject = $oTestObject
$oFake.TestObject.Check1 = 1

$oFake.FakeObject = 1

; in the following line _ComErrorHandler() is not fired even this was already fixed in https://www.autoitscript.com/trac/autoit/ticket/3167
MsgBox(0, "$oFake.FakeObject.Check2", "Result=" & $oFake.FakeObject.Check2)

; in the following line _ComErrorHandler() is not fired and AutoIt ends with "Variable must be of type "Object""
$oFake.FakeObject.Check3 = 1

Func _ComErrorHandler(ByRef $oError)
        #forceref $oError
        ConsoleWrite("! We intercepted a COM Error" & @CRLF)
EndFunc   ;==>_ComErrorHandler

# both .Check2 and .Check3 should fires _ComErrorHandler() and show the console message

 

Edited 3 hours ago by mLipok

[argumentum]

not because a variable is named $oSomething, that is an object. If it is a map, the "ObjEvent("AutoIt.Error", _ErrFunc)" will not trigger unless it was an object.

; Script Start - Add your code below here
; Initialize COM error handler
$oErrorHandler = ObjEvent("AutoIt.Error", _ErrFunc)
Func _ErrFunc($oError)
    ConsoleWrite("!ERROR caught" & @CRLF)
EndFunc

; Create shell object
$oObj = ObjCreate("shell.application")

;The following line should trigger COM error handler (at the last dot).
$oObj.Windows().Item(666).bzzzzzzz
$oObj.Windows().Item(666).bzzzzzzz

That example from "trac: COM Error Handler - not always fires event" is a better starting point.