I\'m trying to debug a 32 bit process dump from a process that ran on an x64 machine. I\'m running an x86 version of windbg on my x64 laptop. I\'ve followed the recommendations here, but I\'m still ge
I have a .Net application dump which captured an exception, I\'m analysing using windbg and interested in the value of a String parameter on one of the methods. I\'ve isolated the String object. My wi
I\'m using DebugDiag for the first time, and I\'m using it on Windows 7 x64.I\'ve created a crash rule for (x86) myprogram.exe, which is guaranteed to crash because I\'ve coded it intentionally to cra
I have an WCF-service running on an server, and occasionally(1-2 times every month) it throws an COMException with the informative message ”Unknown error (0x8005008)”. When i googled for this partic
I\'m trying to track down a memory leak in a C++ application in Windows and I\'ve got a memory dump of the application with a large number of leaked objects. I\'m using Windbg to track them down by do
How do you usually get around this problem? Imagine that a thread crashes inside libc code (which is a system shared library) on Computer1 and then generates a coredump. But the Computer2 on which thi
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
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
Within my application, I use the MiniDumpWriteDump function (see dbghelp.dll) to write a crash dump file whenever my application crashes.
I have an old DLL file which was built with VC++ 6. Now I need to investigate the dump file but I don\'t have its PDB available. The stacktrace reported by WinDbg is also inaccurate.
加载中,请稍侯......