Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[wasm][debugger] Not able to evaluate a static member in a nested class #61462

Closed
ilonatommy opened this issue Nov 11, 2021 · 3 comments
Closed
Assignees
Labels
arch-wasm WebAssembly architecture area-Debugger-mono
Milestone

Comments

@ilonatommy
Copy link
Member

ilonatommy commented Nov 11, 2021

Description

Follow-up issue for 61147.

Reproduction Steps

Create a class in Blazor app:

public static class Foo
{
    public static class Bar
    {
        public static class Abc
        {
            public static int val1 = 10;
        }
    }
}

Add Foo.Bar.Abc.val1 to watch.

Expected behavior

Should return 10 as the value.

Actual behavior

Exception of type 'Microsoft.VisualStudio.Shared.VSCodeDebugProtocol.ProtocolException' was thrown. (Unable to evaluate)

Regression?

No response

Known Workarounds

No response

Configuration

No response

Other information

No response

@ilonatommy ilonatommy self-assigned this Nov 11, 2021
@dotnet-issue-labeler dotnet-issue-labeler bot added area-Debugger-mono untriaged New issue has not been triaged by the area owner labels Nov 11, 2021
@ghost
Copy link

ghost commented Nov 11, 2021

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

Issue Details

Description

Follow-up issue for 61147.

Reproduction Steps

Create a class in Blazor app:

public static class Foo
{
public static class Bar
{
public static class Abc
{
public static int val1 = 10;
}
}
}

Add Foo.Bar.Abc.val1 to watch.

Expected behavior

Should return 10 as the value.

Actual behavior

Exception of type 'Microsoft.VisualStudio.Shared.VSCodeDebugProtocol.ProtocolException' was thrown. (Unable to evaluate)

Regression?

No response

Known Workarounds

No response

Configuration

No response

Other information

No response

Author: ilonatommy
Assignees: ilonatommy
Labels:

untriaged, area-Debugger-mono

Milestone: -

@ilonatommy ilonatommy added the arch-wasm WebAssembly architecture label Nov 11, 2021
@ghost
Copy link

ghost commented Nov 11, 2021

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

Issue Details

Description

Follow-up issue for 61147.

Reproduction Steps

Create a class in Blazor app:

public static class Foo
{
    public static class Bar
    {
        public static class Abc
        {
            public static int val1 = 10;
        }
    }
}

Add Foo.Bar.Abc.val1 to watch.

Expected behavior

Should return 10 as the value.

Actual behavior

Exception of type 'Microsoft.VisualStudio.Shared.VSCodeDebugProtocol.ProtocolException' was thrown. (Unable to evaluate)

Regression?

No response

Known Workarounds

No response

Configuration

No response

Other information

No response

Author: ilonatommy
Assignees: ilonatommy
Labels:

arch-wasm, untriaged, area-Debugger-mono

Milestone: -

@radical radical changed the title [wasm][debugger] Not able to evaluate a static class attribute in a nested class [wasm][debugger] Not able to evaluate a static class member in a nested class Nov 11, 2021
@radical radical changed the title [wasm][debugger] Not able to evaluate a static class member in a nested class [wasm][debugger] Not able to evaluate a static member in a nested class Nov 11, 2021
@lewing lewing added this to the 7.0.0 milestone Nov 11, 2021
@lewing lewing removed the untriaged New issue has not been triaged by the area owner label Nov 12, 2021
@ilonatommy
Copy link
Member Author

Fixed with #61660

@ghost ghost locked as resolved and limited conversation to collaborators Dec 24, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
arch-wasm WebAssembly architecture area-Debugger-mono
Projects
None yet
Development

No branches or pull requests

2 participants