I have an application that sometimes causes a BSOD on a Win XP machine. Trying to find out more, I loaded up the resulting *.dmp file (from C:\Windows\Minidump), but get this message when in much of the readout when doing so: Symbols can not be loaded because symbol path is not initialized. * * The Symbol Path can be set by: ...
I currently capture MiniDumps of unhandled exceptions using SetUnhandledExceptionFilter however at times I am getting "R6025: pure virtual function". I understand how a pure virtual function call happens I am just wondering if it is possible to capture them so I can create a MiniDump at that point. ...
Currently we call MiniDumpWriteDump with the MiniDumpNormal | MiniDumpWithIndirectlyReferencedMemory flags. That works just fine for internal builds in Debug configuration, but isn't giving as much information as we need in Release configuration. In Release, the minidump data contains enough stack information for the debugger to work ou...
Is there a way to view the register contents in each stack frame in a crash dump? The registers window seems to contain the registers when the exception occurred but it would be useful to be able to see their contents in each stack frame. ...
I have created a minidump using win32 api [DllImport("DbgHelp.dll", SetLastError = true)] private static extern bool MiniDumpWriteDump( dmp file is successfully created. i am trying to open this *.dmp file in another visual studio instance to locate the place of the crash, in visual studio --> FILE--> open project the dmp file op...
In a way following on from reading a windows *.dmp file Having received a dump file from random customer, running the debug session to see the crash, you often find it is in a MS or other third party library. The next issue is that you may not have knowledge of the PC setup to such an extent that you can ensure you have the actually mo...
I have a MFC SDI application which during startup loads a DLL. I am only able to view the source code and use the DLL but not changing & recompiling it. The situation now is that, whenever the DLL encouner an error it will call exit() such as below. bool Func() { // .. do something here if (error) { exit(999); } } In my MFC appl...
A customer is attempting to capture a minidump of a hang. He fires up WindDbg and successfully attaches to the process. WinDbg displays its header: Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. and the loaded modules are enumerated. He enters a dump command: .d...
I have a native release dll that is built with symbols. There is a post build step that modifies the dll. The post build step does some compression and probably appends some data. The pdb file is still valid however neither WinDbg nor Visual Studio 2008 will load the symbols for the dll after the post build step. What bits in either ...
Is there any way to analyze app-crash minidumps (e.g. created by SetUnhandledExceptionFilter, or minidumpwritedump()) with source, using Visual Studio 2008 Express? I generally do this at work using "real" versions of VS, but when trying to get it to work on my personal projects (using VS 2008 Express) it tells me "There is no source ...
I am curious about the IDs that are used to identify items in winqual. I assume it is some sort of hash. Is this published? Hash of the module name, its version and an offset? That seems appropriate but the size is too small to cover the possibilities unless some truncation/lossy algorithm is used. This seems to be generated with th...
I have to perform some post mortem debugging on a C++ project. Known way to perform is to set the cdb debugger as a minidump generator and to process the dumps collects afterwards. I read nearly the whole web and I didn't find a solution to produce a minidump with the name of the process that has crashed Is there a way to set AeDebug\De...
I want to use the MiniDumpWriteDump function to create some custom dump files (mainly, i want to export a dump file that contains the minimum amount of information for the thread callstacks), but i am having difficulties defining the structures that need to be passed as a parameter to the callback function [StructLayout(LayoutKind.Expli...
I am trying to build some automated crash dump analysis, but I cannot get cdb or windbg to load my crash dumps. They load just fine in VS 2008. When I run dumpchk.exe on the file, I get: Loading Dump File [c:\devx86\temp\ErrorDump.mdmp] User Mini Dump File: Only registers, stack and portions of memory are available ERROR: Memory rang...
We have an in-proc crash handler which is using MiniDumpWriteDump() from DbgHelp to write a minidump is case of a process crash. I know its not the best way to do it, however, at the moment we do not have other option. The problem is: one certain executable always creates 0 byte dumps. But it works well for other processes. What could...
When ngen is executed on a .NET managed application at installation time, and a crash dump is retrieved from Windows Error Reporting for the app, how can you use it to see a stack trace, variables, etc.? Here's some background related to the question: We have a .NET app that gets ngened at installation. When it crashes due to an unhandl...
Hi I am not able to create minidump form my process by changing system setting.So my Question is Will system create a minidump for user process when they crashes If yes , which setting i need to configure Or do i have to create minidump programmatically. How much effective minidumps are while investigating a crash ...
I've used minidumps on many game projects over the years and they seem to have about a 50% chance of having a valid call stack. What can I do to make them have better call stacks? I've tried putting the latest dbghelp.dll in the exe directory. That seems to help some. Is Visual Studio 2008 or 2010 any better? (I'm still on VS 2005). T...
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: PMINIDUMP_USER_STREAM_INFORMATION UserStreamParam and describes the parameter thusly: UserStreamParam [in] Pointer to an array of MINIDUMP_USER_STREAM_...
I am debugging a minidump in WinDbg and the Visual Studio 2005 debugger and they produce different results. WinDbg gets it wrong When doing KP in WinDbg, the relevant part of the stacktrace is: 0bb6ef30 0a4a25b8 MyModule!SomeClass::methodB( void * buffer = 0x05d8d800, int bufferLen = 1797233953, ...