-
Notifications
You must be signed in to change notification settings - Fork 256
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
ClrMD is not working from within a .NET 6 single-file application on Windows #975
Comments
What version of clrmd are you using? The latest on nuget: 2.0.226801? |
Yes, that's the one:
|
AFAIK this is actually due to an issue with create-dump, not with ClrMD. See this issue: dotnet/diagnostics#3065. When I last debugged this, there was not enough data being placed into the crash dump for any debugger to make sense of single-file dumps (ClrMD included). I'm happy to take a closer look if you find that's not the case. |
I noticed in the issue linked to by @leculver (dotnet/diagnostics#3065) that near the end of the discussion there that @mikem8361 mentions that: "It is against Windows policy to ship/redistribute the fixed dbghelp/dbgcore/dbgeng with dotnet-dump. This fix will shipping in a future Windows service release." Well it seems that this has happened as the problem I was seeing has 'self healed' without me even having to recompile my test program! Thanks for fixing this. I'm unsure if I should close this myself (since it wasn't me who did the hard work of fixing the problem) so I'll leave the issue open so that the right person can close this with a suitable comment. |
This was working for me in .NET 5. A simple program can show the problem:
For .NET 5 the publish profile is:
With .NET 5 I get the following output:
For .NET 6 the publish profile is:
For .NET 6 I get the following output:
I used VS2022 for this program.
It would be nice to see this working again. I've used it in real programs to list the stack traces for all threads to a file. This allows me to have users send me a simple text file which along with other information on our app has the stack traces which helps in diagnosing deadlocks.
The text was updated successfully, but these errors were encountered: