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
When I try to set a breakpoint in the code before I ran it, nothing happens. The breakpoint won't be added.
When I debug and step into the method, then it shows me different code - the state machine code of the async operation.
How do I see this before debugging? why do I see different code that I can't debug?
How To Reproduce
Load some module with async code, go to the async method and try adding breakpoints.
Expected Behavior
Add breakpoints
Actual Behavior
Won't add a breakpoint
Additional Context
f
The text was updated successfully, but these errors were encountered:
This is probably occurring because you have this option enabled in dnSpy:
Enabling this option results in the debug info for the sync method being generated with regard to the original state machine as opposed to the lifted async code.
This is probably occurring because you have this option enabled in dnSpy:
Enabling this option results in the debug info for the sync method being generated with regard to the original state machine as opposed to the lifted async code.
yea I think this is it haha.
Did this change from the old dnspy? because I remember you had to check this option to actually see the async code
dnSpyEx version
v6.5.1
Describe the Bug
.NET 6, I have async code.
When I try to set a breakpoint in the code before I ran it, nothing happens. The breakpoint won't be added.
When I debug and step into the method, then it shows me different code - the state machine code of the async operation.
How do I see this before debugging? why do I see different code that I can't debug?
How To Reproduce
Load some module with async code, go to the async method and try adding breakpoints.
Expected Behavior
Add breakpoints
Actual Behavior
Won't add a breakpoint
Additional Context
f
The text was updated successfully, but these errors were encountered: