You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Static fields evaluation works only in an instance method. Otherwise, we have to address the field with the fill namespace. It should not be required as the field belongs to locals.
Static fields in DIMs:
Reproduction steps:
in interface IDefaultInterface in src\mono\wasm\debugger\tests\debugger-test\debugger-test.cs we have a static field: defaultInterfaceMember. Its visibility in interface's method is tested in EvaluateLocalsInDefaultInterfaceMethodStatic.
Current behavior:
When we useEvaluateOnCallFrameAndCheck with defaultInterfaceMember as evaluated value inside of interface's method, it fails. We would need to pass the full name: IDefaultInterface.defaultInterfaceMember to get the right value. In this location we should have access to the static fields without referencing to it with a full name.
Expected behavior: EvaluateOnCallFrameAndCheck with defaultInterfaceMember passed (without interface name) should result in "defaultInterfaceMember".
Static fields in a static class evaluated from a static method of this class.
Static fields in an instance class, evaluated from a static method of this class.
The text was updated successfully, but these errors were encountered:
Tagging subscribers to this area: @thaystg
See info in area-owners.md if you want to be subscribed.
Issue Details
Reproduction steps:
in interface IDefaultInterface in src\mono\wasm\debugger\tests\debugger-test\debugger-test.cs we have a static field: defaultInterfaceMember. Its visibility in interface's method is tested in EvaluateLocalsInDefaultInterfaceMethodStatic.
Current behavior:
When we useEvaluateOnCallFrameAndCheck with defaultInterfaceMember as evaluated value inside of interface's method, it fails. We would need to pass the full name: IDefaultInterface.defaultInterfaceMember to get the right value. In this location we should have access to the static fields without referencing to it with a full name.
Expected behavior: EvaluateOnCallFrameAndCheck with defaultInterfaceMember passed (without interface name) should result in "defaultInterfaceMember".
Author:
ilonatommy
Assignees:
ilonatommy
Labels:
arch-wasm, area-Debugger-mono
Milestone:
-
ghost
added
the
untriaged
New issue has not been triaged by the area owner
label
Jun 2, 2022
ilonatommy
changed the title
[wasm][debugger] Enable onCallFrame evaluation of static fields in Default Interface Method
[wasm][debugger] Enable onCallFrame evaluation of static fields in classes/interfaces from a static method.
Jun 7, 2022
Static fields evaluation works only in an instance method. Otherwise, we have to address the field with the fill namespace. It should not be required as the field belongs to locals.
Reproduction steps:
in interface
IDefaultInterface
in src\mono\wasm\debugger\tests\debugger-test\debugger-test.cs we have a static field:defaultInterfaceMember
. Its visibility in interface's method is tested inEvaluateLocalsInDefaultInterfaceMethodStatic
.Current behavior:
When we use
EvaluateOnCallFrameAndCheck
withdefaultInterfaceMember
as evaluated value inside of interface's method, it fails. We would need to pass the full name:IDefaultInterface.defaultInterfaceMember
to get the right value. In this location we should have access to the static fields without referencing to it with a full name.Expected behavior:
EvaluateOnCallFrameAndCheck
withdefaultInterfaceMember
passed (without interface name) should result in "defaultInterfaceMember".The text was updated successfully, but these errors were encountered: