I\'ve got a whole bunch of minidumps which were recorded during the runtime of an application through MiniDumpWriteDump. The minidumps were created on a machine with a different OS version than my dev
COM Excel AddIn, C#, VS 2008, Excel COM Addin, tested on test VM, works fine Customer installed and got blue screen, have no clue why.
Got this callstack when I open a Windows crash dump in Visual Studio 2005: >myprog.exe!app_crash::CommonUnhandledExceptionFilter(_EXCEPTION_POINTERS * pExceptionInfo=0x0ef4f318)Line 41C++
When my application crashes it generates a minidump to allow post mortem debugging. I use the options MiniDumpWithIndirectlyReferencedMemory and MiniDumpWithPrivateReadWriteMemory.
I see some conflicting opinions about mini dumps for .NET debugging开发者_开发百科, for example;
I want my app to create a mini dump to help debug unhanded exceptions. I may not know what type of mini dump I will want until after the dump has been created, so what combinations of MINIDUMP_TYPE f
There is native C++ application that hosts several .net components. When some error occurs this application creates mini dump using MiniDumpWriteDump function. Question here what is minimum set of
There are a few related questions on SO - but have not found the answer - I would like to generate a \"signature\"/bucket id to report a minidump/crash back to our issue tracking system.Since MS alre
I have a mixed-mode C++/CLI application which uses WPF. Crashes from our customers are reported as minidumps to our own server.
I want to write a utility that in the event of a fatal error, a minidump dmp file is created.I\'m using the clrdump api and that seems fairly straightforward.
加载中,请稍侯......