Re: memorydump in vista

"Andre Kaufmann" <andre.kaufmann_re_move_@xxxxxxxxxxx> wrote in message news:%23xLdM8EgHHA.4536@xxxxxxxxxxxxxxxxxxxxxxx
Willy Denoyette [MVP] wrote:
[...]
Advantages:

a) Don't need to reproduce a problem on my developer machine
b) I can evaluate bugs much faster, than I would be able to do with



Agreed, In case of a crash, that is from an unhandled exception handler, however, I was talking about simply calling Dbghelp.dll API's from a running process.

Ok it's not that simple, as in the case of a crash. Though it's possible to (simplified) "simulate a crash". E.g. John Robbins has written a very good book about crash dumps and how to create them.


Yep, I have it on my desk ;-)

But I agree - in pure C# code it's not possible - don't know if Vista supports a simple function for dump file creation.


Not that I know of, the latest dbghelp is what I'm using.

The other simple solution would be to force a crash. Unfortunately this can be done only once ;-9.

[...]

Note that,while analysis of a "native code" minidump is just a snap ;-), post-mortem analysis of a "JITted code" minidump can be a daunting task, even for an expert.

Agreed. I haven't tested it by myself (yet), but it surely isn't that simple to evaluate managed crash dumps. To debug deadlocks it should be also sufficient to dump the call stacks of all running managed threads.


Don't you mean "all running threads"? You can't distinct managed from unmanaged threads as there is no difference at this level.
I've done some post-mortem analysis using dbghelp, and found out that you need at least the following MINIDUMP_TYPE
MiniDumpWithDataSegs, & MiniDumpWithPrivateReadWriteMemory , to be able to get somewhere with SOS.DLL. "Managed" threads only exist (though, they map to OS threads) at the CLR level and therefore you need the SOS extentions if you need to analyse "managed threads" and other CLR related datastructures.
Willy.




.

Relevant Pages

  • Re: Propose for Several Dump types
    ... >> us it without knowing anything else. ... >> receive it in email whenever a crash occured. ... I still think ascii format dump can not replace the minidump. ... | UNIX since Zilog Zeus 3.20 ...
    (freebsd-arch)
  • Re: memorydump in vista
    ... Agreed, In case of a crash, that is from an unhandled exception handler, however, I was talking about simply calling Dbghelp.dll API's from a running process. ... post-mortem analysis of a "JITted code" minidump can be a daunting task, ... I haven't tested it by myself, but it surely isn't that simple to evaluate managed crash dumps. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: C++ parser for diagnostics
    ... I was thinking of this code beyond just exception handling, but the minidump ... > Hi Dave! ... >> line run before the crash. ...
    (microsoft.public.dotnet.languages.vc)
  • RE: IIE stopped unexpectedly
    ... We would need to look at crash dumps to find out why this issue occurred. ... Microsoft Developer Support ... Internet Information Server ...
    (microsoft.public.inetserver.iis.security)
  • Re: VMIC reflective memory crash
    ... VMIC memory is shifted 8 bytes and VMS crashes. ... When VMS crashes, are you getting crash dumps? ...
    (comp.os.vms)