Re: memorydump in vista
- From: Andre Kaufmann <andre.kaufmann_re_move_@xxxxxxxxxxx>
- Date: Mon, 16 Apr 2007 19:46:28 +0200
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.
But I agree - in pure C# code it's not possible - don't know if Vista supports a simple function for dump file creation.
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.
Willy.
Andre
.
- Follow-Ups:
- Re: memorydump in vista
- From: Willy Denoyette [MVP]
- Re: memorydump in vista
- References:
- memorydump in vista
- From: Dirk Reske
- Re: memorydump in vista
- From: Willy Denoyette [MVP]
- Re: memorydump in vista
- From: Andre Kaufmann
- Re: memorydump in vista
- From: Willy Denoyette [MVP]
- memorydump in vista
- Prev by Date: store web.config setting in SQL table
- Next by Date: Tray process question
- Previous by thread: Re: memorydump in vista
- Next by thread: Re: memorydump in vista
- Index(es):
Relevant Pages
|