-
Notifications
You must be signed in to change notification settings - Fork 802
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
Fix 7456, 3704, 12019 (debug scopes, self arg, incorrect information display on shadowing) #12018
Conversation
…ion display on shadowing) dotnet#12018
I'll add a bit more technical detail about how the removal of shadowing works First, assume the IL Debug Scopes actually form a well-formed tree, and there is an IL instruction range from 0 to 9, with these scopes with the indicated locals defined
The idea is to split and rename to these non-nested scopes with the indicated variable mappings
There is no intrinsic need to have nested scopes - splitting them is ok as long as we have a root scope. |
I added a fix for #12029 to this PR |
VS2019 had a regression where not all method local scopes were being emitted to the PDB Variables do not show in debugger in top-level program #7456
Self/this is not known in debugging (unless called "this") #12019
We've long had a problem with shadowed bindings Debugger info is incorrect for shadowed bindings #3704. This fixes this by
There is no change to IL, just the PDB
Fix Out-of-scope locals are shown uninitialized in debugger when debugging top-level module code #12029
An example is shown below. Note the variable name in the locals window, and not that the hover-tip now gives the correct result.
Fix for #1 demonstrated:
Fix for #2 demonstrated:
Fix for #3 demonstrated:
Fix for #4 demonstrated: