crash-dumps

问题 Is there a way to WinDbg in pure headless mode ? My use case is that I should be able to imitate "!analyze -v" command for a minidump on command line without launching WinDbg GUI. 回答1: With the Debugging Tools for Windows, there is also cdb , the console debugger. To debug a crash dump, use the -z "<dump>" option. To run a command immediately, use -c "<command>" . To output everything into a file you can redirect the output with a usual DOS > <file> or open a log file using .logopen <file> .

问题 I want to parse the full crash dump (*.dmp) file and get the private bytes data. I know that VMMap of SysInternals can tell me how much my private bytes, heap etc are all but what I need is if I have the dump, I should be able to parse it and get the Heap (managed Heap) Structure and data in the heap. I am already done with this by reading the PEB and then walking through heaps. What I am not able to figure out is how to read the private bytes (other than Heap, which is supposed to be the

问题 I have a crash dump for a customer's application built with a very old version of our dll (release build, don't have original symbols) that I've been analyzing in WinDbg. In order to get more information, I rebuilt the dll in release mode, with symbols this time, using the same compiler version and I believe the same settings as when the dll was originally built. I added the symbol file to my symbol path, but the WinDbg extension !itoldyouso tells me the module in the dump doesn't match the

问题 I have a crash dump for a customer's application built with a very old version of our dll (release build, don't have original symbols) that I've been analyzing in WinDbg. In order to get more information, I rebuilt the dll in release mode, with symbols this time, using the same compiler version and I believe the same settings as when the dll was originally built. I added the symbol file to my symbol path, but the WinDbg extension !itoldyouso tells me the module in the dump doesn't match the

问题 I've got a java application that half the time just hangs, and the other half the JVM crashes. Is there a tool I can use to see what's going on that makes it hang and/or crash? I'm using CentOS 5.6 回答1: There are two different cases. Application crash: Was that an OOM? NPE? What was the exception? If there was jvm crash you will see hs_err_.log (http://java.sun.com/j2se/1.5/pdf/jdk50_ts_guide.pdf) Looking at the file you may see if your own JNI caused a crash or JVM bug. Application Hang: I

问题 I've got a java application that half the time just hangs, and the other half the JVM crashes. Is there a tool I can use to see what's going on that makes it hang and/or crash? I'm using CentOS 5.6 回答1: There are two different cases. Application crash: Was that an OOM? NPE? What was the exception? If there was jvm crash you will see hs_err_.log (http://java.sun.com/j2se/1.5/pdf/jdk50_ts_guide.pdf) Looking at the file you may see if your own JNI caused a crash or JVM bug. Application Hang: I

问题 How do I use WinDbg for analyzing a dump file? 回答1: Here are some general steps that will get you on your way: First, you must change your compiler's settings so that it creates PDB files, even for release builds. Later versions of the Visual C++ compiler do this by default, but in many versions of Visual C++ you must do this yourself. Create program database files, and then keep an archive of those files along with each build of your application. It is critical that every build of your

问题 How do I use WinDbg for analyzing a dump file? 回答1: Here are some general steps that will get you on your way: First, you must change your compiler's settings so that it creates PDB files, even for release builds. Later versions of the Visual C++ compiler do this by default, but in many versions of Visual C++ you must do this yourself. Create program database files, and then keep an archive of those files along with each build of your application. It is critical that every build of your

问题 I'm currently writing a JNI project where I'm getting the following error log when trying to run my Java code. It tells me that the problematic frame is a jvm.dll one, and in trying to isolate the problem, I'm trying to work out where exactly my problem is (in the JVM vs. my native code) I've attached the thread section of the log, and can append the rest if needed. I also tried reinstalling the JVM. A fatal error has been detected by the Java Runtime Environment: EXCEPTION_ACCESS_VIOLATION

问题 I am working with a legacy VB6/COM application which sometimes causes Windows 7 to crash. I have now generated a .dmp file of one of these crashes using the ProcDump tool from Sysinternals. However, I have never worked with dump files before. Which resources would you recommend for getting started with dump file analysis? 回答1: Some more links that might be usefull WinDBG and tools: https://developer.microsoft.com/en-us/windows/hardware/download-windbg .Net extension for WinDBG: https://docs