minidump

I use Cmake + mingw to compile my project. Since some unknown moment my program started to crash on startup and i figured out how to make windows make minidump for my crashing application. I would use GDB to directly debug my application, but when i use GDB the program doesn't crash. Google breakpad contain tool to convert minidumps to coredumps, so i tryed to compile google breakpad but it seems breakpad is not windows solution. I'm searching for solution how to inspect minidump and find why my program crashes on start. How do you do it? Sergei Kurenkov You don't need to analyze minidumps.

MiniDump向导应用程序允许在不编写代码的情况下尝试MiniDumpWriteDump和MiniDumpCallback函数。可以指定将传递给MiniDumpWriteDump函数的MINIDUMP_TYPE标志的组合，并且可以在一系列对话框中响应MiniDumpCallback调用。 如何使用MiniDump Wizard 启动MiniDump向导时，它会显示一个对话框窗口，允许您选择将传递给MiniDumpWriteDump函数的MiniDump类型标志。在同一对话框中，可以指定要响应的回调类型。 对话框还允许指定目标进程。您可以指定目标的进程标识符（pid），也可以为小型转储向导进程本身创建小型转储。为了探索为小型转储向导进程创建的小型转储的内容，提供了MiniDumpWiz.pdb文件。 在第一个对话框中指定所有设置后，按Next将创建小型转储（如果未选择回调选项），或显示指定调用小型转储回调函数的对话框页，您可以在其中检查传递给回调的数据并响应回调调用（通过使用对话框控件修改回调的返回值、MINIDUMP_CALLBACK_OUTPUT structure的内容，或同时修改两者）。 微型转储文件将被称为MiniDumpWiz.dmp。目前无法更改其名称（这是为了使应用程序尽可能简单）。 MiniDump Wizard 界面介绍 主界面 启动MiniDump

函数MiniDumpCallback 如果要自定义MINIDUMP类型标志无法访问的MINIDUMP的内容，可以使用MiniDumpCallback函数。这是一个用户定义的回调，当MiniDumpWriteDump需要用户决定是否将某些数据包含到minidump中时，它将被调用。借助此功能，我们可以完成以下任务： 从minidump的模块信息中排除可执行模块（全部或部分） 从minidump的线程信息中排除线程（全部或部分） 将用户指定范围内存的内容包含到小型转储中 让我们看看MiniDumpCallback函数的声明 BOOL CALLBACK MiniDumpCallback( PVOID CallbackParam, const PMINIDUMP_CALLBACK_INPUT CallbackInput, PMINIDUMP_CALLBACK_OUTPUT CallbackOutput ); 函数接收三个参数。第一个参数（ CallbackParam ）是回调函数的用户定义上下文（例如，指向C++对象的指针）。第二个参数（CallbackInput）包含MiniDumpWriteDump传递给回调的数据。第三个参数（CallbackOutput）包含回调返回到MiniDumpWriteDump的数据（该数据通常指定应包含在minidump中的信息）。

I'm trying to "Debug Managed Memory" with Visual Studio 2015 Enterprise Edition. The file is at 1.2GB and after while loading I get the error message "Memory analysis could not be completed due to insufficient memory" after have been pressing "Debug Managed Memory" What can I do to still be able to look into the memory with the pdb files? Can I start Visual Studio 2015 with more memory (the computer has 25 GB memory free) I guess it has to do with Visual Studio being running with x86. It could be related to VisualStudio bug see the following link https://connect.microsoft.com/VisualStudio

I'm working on generating minidumps for my managed app. Here's what I have so far: I've set up an exception filter as in this article . In the filter I call MiniDumpWriteDump. I've been able to load the resulting dump in the VS debugger, browse the call stack and view the values of locals. However, when optimizations are enabled in my project, the values of locals are inaccessible (I get "The value of the local or argument 'x' is unobtainable at this time" ). Now, I know why this happens - optimizations can do things like reuse locals, which means the compiled code doesn't reflect the source

I've been trying to install the 'Debugging Tools', in order to try to analyse the dump file a server-crash (Windows Server 2008 R2). I used to do this in the past, but I cannot find how to install / locate the Debugging Tools for Windows 7. I've read this KB article: http://support.microsoft.com/kb/315263 . I've then tried to download the 'Debugging Tools for Windows' from the following article ( http://msdn.microsoft.com/en-us/windows/hardware/gg463009.aspx ). I chose the 'Install Debugging Tools for Windows as a Standalone component', downloaded the file and installed. It did install