-
-
Notifications
You must be signed in to change notification settings - Fork 484
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
Not able to debug assembly #371
Comments
Hey, I'm unable to reproduce this issue using the latest dnSpyEx CI build. Both .net framework and .net-x64 compiled binaries have no trouble debugging the ILSpy build you linked. |
Oh Gosh! |
Starting the debugging with either ILSpy.dll or ILSpy.exe works for me. dnSpy should identify .NET apphost .exe files and debug them appropriately |
OK, then I've hit 100% repro trying to debug ILSpy.exe are there any hints how could I dig more info to track this case down? |
Honestly, I have no clue what could be going on here since CorDebug does not seem to be reporting any kind of meaningful error code to indicate what is actually going wrong. Are you perhaps debugging ILSpy.exe with the .NET Framework engine rather than the .NET engine? |
is it possible to debug dnSpy while it tries to debug ILSpy? |
yes, it was .NET in the drop-down control "Debug engine" |
Yes you can either use multiple instances of dnSpy:
or you can just pull in the dnSpy source from GitHub and open it in an IDE on windows. |
dnSpyEx version
6.5.1
Describe the Bug
I'd like to investigate some weird fresh bug in latest ILSpy and I wanted to debug it,
but all of a sudden I"ve hit strange error on debug start:
from ILSpy about:
ILSpy version 9.0.0.7814-preview2+c66733f353a24174dbc7c9283333b50f796cd426
.NET version 8.0.8+08338fcaa5c9b9a8190abb99222fed12aaba956c
How To Reproduce
Download CI build from master, eg: ILSpy version 9.0.0.7814-preview2
ILSpy 9.0.0.7814-preview2 (Debug)
Expected Behavior
Debugger starts up successfully
Actual Behavior
see error window above
Additional Context
No response
The text was updated successfully, but these errors were encountered: