I have observed on Windows 2008 the Windows Error Reporting crash dumps get staged in the folder: C:\Users\All Users\Microsoft\Windows\WER\ReportQueue Which, starting with Windows Vista, is an alias for: C:\ProgramData\Microsoft\Windows\WER\ReportQueue
After ANR happens, you would find call stack of related process at /data/anr/traces.txt After application crashes, you might find call stack of crashed application under /data/tombstones directory.
Use the sos !EEStack command: 0:007> .load sos 0:007> !EEStack See SOS.dll (SOS Debugging Extension)
I found it. It moved, it’s no longer inside General/Diagnostics… It’s in Privacy/Diagnostics.
Note that creating a minidump from inside the “failing” process (or even thread) itself is not trivial or might not be accurate (also MiniDumpWriteDump function’s Remarks). Besides, if your process is in such anger that you might need to write a crash dump, the whole situation is typically so hosed, that even attempting to create … Read more
Yes, it is. You can change /proc/sys/kernel/core_pattern to define the pathname used to generate the corefile. For more, see man core example: echo ‘/tmp/core_%e.%p’ | sudo tee /proc/sys/kernel/core_pattern # `tee’ instead of > so that # opening happens in the # elevated process would cause all future core dumps to be generated in /tmp and … Read more
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 … Read more
Differences between full memory dump files and mini memory dump files A memory dump file can collect a variety of information. Typically, a support engineer must have all the contents of virtual memory to troubleshoot a problem. In other cases, you might want to capture less information to focus on a specific problem. The debugger … Read more
The much advertised feature that Visual Studio 2010 allows you to debug crash dump files and step through the managed source code comes with a gotcha: it works only for .NET 4.0 assemblies. Here are the steps: Create a crash dump file on another computer using the Task Manager Open the solution in VS2010 Open … Read more
Install WinDbg. You need to make sure you get the correct version x86 or x64 depending on your dump. Here is a direct link to the download for x86. On that, you need to ensure you took the correct dump. You can use Task Manager to create the dump file (right click on process -> … Read more