Debugging (managed) MiniDumps displays the writing-callstack and not the exception-callstack - by Jochen Kalmbach

Status : 

  By Design<br /><br />
		The product team believes this item works according to its intended design.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


1
1
Sign in
to vote
ID 387985 Comments
Status Closed Workarounds
Type Bug Repros 2
Opened 12/14/2008 6:54:20 AM
Access Restriction Public

Description

The new debugging of managed (full) minidumps in VS2010 CTP works, but it shows the "wrong" callstack. It shows the callstack of the "minidump-writer" and not the callstack of the exception!
Therefor the minidump-analysis is useless...
Sign in to post a comment.
Posted by Stefan Monov on 9/9/2011 at 5:15 AM
Hello.

You said the CLR doesn't support managed processes taking their own dumps. Is this still true?
Posted by Andrew [MSFT] on 2/11/2009 at 2:44 PM
Hello,

Thank you for taking the time to file this bug. Currently the CLR does not support managed processes taking their own dumps. The way to get an accurate dump is to run the process under the Visual Studio Debugger and set the debugger to break on the first chance exception (via: Debug -> Exceptions) and then save the dump through the Visual Studio Debugger (Debug -> Save Dump As). This should give you the correct call stack in the dump file.

Best Regards,
Andrew Hall
Visual Studio Debugger