I downloaded开发者_高级运维 and installed the latest version (6.12.2.633) of Debugging tools for windows. Running it with .NET 4.0. When I run !address -summary command seem like its output is differe
I have WOW64 crash dumps with call stack information like: 0018fb00 77c06a8b 0018fbc8 0018ffc4 0018fc18 ntdll_77bc0000!ExecuteHandler2+0x26
I\'ve been struggling now for some time with a crash in a C# application that also uses a fair share of C++/CLI modules that are mostly wrappers around native libraries to access device drivers.
A 32bit .net application, running on a 32 bit machine, ran into an OutOfMemoryException. I then took a full memory dump, and although using WinDbg I can verify that a lot of memory is being used, I wo
I\'m trying to investigate a really nasty software crash which is possibly related to a managed heap corruption (since it happens during a garbage collection). Using WinDbg with the (SOS) !gchandles c
I\'m trying to analyse a crash dump of MS BizTalk service, which is constantly consuming 100% CPU (and I assume that\'s because of our code :) ). I have a couple of dumps and the stack trace of the bu
This is a very quick question. I searched and can\'t seem to find the windbg command that would show what options exist in a minidump file.
The task - when the application crashes, it is required to find the crash cause. I saw recommendations to take the crash dump with AdPlus and then load it into WinDbg for analysis.
I\'m following some WinDbg instruc开发者_运维知识库tions from the CodeProject tutorial. To start a server, I can get this to work from the command line fine:
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
加载中,请稍侯......