I am forcibly crashing the process and trying to analyze the crash dump. I am facing the race condition between crash the process and crash dump generation (flush).
Is it possible to symbolicate MonoTouch crash dumps and get line numbers out of them? If so, how is it done?
Following question describe for windows H开发者_如何学编程ow to create minidump for my process when it crashes?
I failed to analyze the dump file using Windbg. Any help would be greatly appreciated. Here are my WinDbg settings:
I have an application which is mostly native code written in C: Simon Tatham\'s Puzzles. When I catch a crash (with a signal handler), a Java backtrace will only tell me the vague area of the problem:
I\'m working on a Python application. Sometimes the interpreter crashes when in a third party C++ DLL.
To get the dump file (for crashes) I am using the userModeProcessorDumper.exe. Now the question is how to read this file (to see the stack information). Regarding this I have couple of questions
How to ensure a dump file is written by C++ application in case of exception which is not handled. For example 开发者_运维技巧if division by zero is not handled then how do ensure Dump is written.
I have a simple program: int ExecuteCommand(wchar_t* commandLine) { STARTUPINFO si; PROCESS_INFORMATION pi;
Our C# application calls MinidumpWriteDump upon an unhandled exception. I have received some crash dumps from users where i cannot seem to open the crash dump with SOS and see the exception that caus
加载中,请稍侯......