Using WER and clrstack -p
Hi,
I've managed to get WER up and running and downloaded some cab files for my test application. I was hoping the functionality you would get from these mdmp files would be similar to a normal minidump. Although I can get the stacktrace using !clrstack, what I really want is !clrstack -p which doesn't seem to work.
Could anyone give me any pointers to how to get useful information out of the mdmp file? Even just finding which objects on the stack are null reference pointers etc would be helpful.
Thanks,
Matt
[530 byte] By [
Shinmen] at [2008-2-13]
Hi Matt,
I had an email exchange with the lead Developer of the WER client and a senior Program Manager on the CLR team, and they felt that the minidump format for a CLR managed crash will really only expose a list of managed threads, their callstacks (w/o params) and also the current managed exception object.It sounds like what you need is more than the minidump in this case. A heap dump should get you what you want.
With the heap dump, you can use '!dumpstackobjects'.
If you contact the WER Services team, they will set up a special collection rule for a particular event ID to collect a dump with heap in place of the default minidump. To conatct the WER Services team, simply send an email to WER@microsoft.com with 'Using WER and clrstack -p' in the subject line and ask for heap dump collection on your event ID (...provide the event ID as well).
In the near future we will offer the ability for you to request a heap dump througth WER Services on https://winqual.microsoft.com.
Kind regards,
-Jason
