[wasm][debugger] Fix exception reason on evaluation of method that throws

[ilonatommy]

In test: DebuggerTests.EvaluateOnCallFrameTests.EvaluateSimpleMethodCallsError for case evaluating: this.ParmToTestObjException.MyMethod()

is failing because:

(2,43): error CS1061: 'string' does not contain a definition for 'MyMethod' and no accessible extension method 'MyMethod' accepting a first argument of type 'string' could be found (are you missing a u    sing directive or an assembly reference?)

but should fail because ParmToTestObjException threw an exception.

Script used to compile the expression:

string this_ParmToTestObjException_fee35 = "System.Exception: error2"; return (this_ParmToTestObjException_fee35.MyMethod() );

Suggested in: #66654 (comment)

[ghost]

Tagging subscribers to this area: @thaystg
See info in area-owners.md if you want to be subscribed.

Issue Details

---

null

Author:	ilonatommy
Assignees:	-
Labels:	untriaged, area-Debugger-mono
Milestone:	-

[ghost]

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

---

In test: DebuggerTests.EvaluateOnCallFrameTests.EvaluateSimpleMethodCallsError for case evaluating: this.ParmToTestObjException.MyMethod()

is failing because:

(2,43): error CS1061: 'string' does not contain a definition for 'MyMethod' and no accessible extension method 'MyMethod' accepting a first argument of type 'string' could be found (are you missing a u    sing directive or an assembly reference?)

but should fail because ParmToTestObjException threw an exception.

Script used to compile the expression:

string this_ParmToTestObjException_fee35 = "System.Exception: error2"; return (this_ParmToTestObjException_fee35.MyMethod() );

Author:	ilonatommy
Assignees:	ilonatommy
Labels:	arch-wasm, area-Debugger-mono
Milestone:	-

[thaystg]

This is fixed by the new debugger.