I am trying to use MiniDumpWriteDump() API to dump a crashed process B from another process A. I am doing this because MSDN said so:
I\'m looking at a crash dump. Some variables seem perfectly viewable in windbg, while others just say \"memory access error\". What causes this? Why do some variables have sensical values while others
I am currently trying to design a memory dump tool that could get the memory dump of a crashed process from another process. But I am totally new to this and I want to take this as an opportunity to g
With the dump debugging su开发者_C百科pport in .NET 4.0 we are looking into automatically (after asking the user of course :) creating minidumps of C# program crashes to upload them to our issue track
I\'m new to WER (actually, just registered a few days ago). I\'ve managed to establish an account and map my test application to it.
I work on a large application, and frequently use WinDbg to diagnose issues based on a DMP file from a customer.I have written a few small extensions for WinDbg that have proved very useful for pullin
The MiscInfoStream in a minidump file contains the process create time. I\'d like to find out how long the process has been running for before the crash. Does a minidump file contain the exception tim
If I use a class/method like the one described here how can I get the description/address of the call at the top of the stack?
I am interested in what useful things developers put in the user stream data structure that can be embedded in minidumps.MSDN describes the parameter for MiniDumpWriteDump as such:
I am not able to create minidump form my process by changing system setting. So my Question is : Will the system create a minidump for a user process when it crashes
加载中,请稍侯......