Error Reporting Files
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Fri, 14 Oct 2016 17:18:50 GMT by s_ac15 (squid/3.5.20)
MiskellyMay 24, 20073 0 0 0 If you’re a software developer, chances are that you have written an application, and this application has crashed. When this happened, it probably put up a dialog that looks something like this: How do you figure out what went wrong? Strategy #1:
Disable Windows Error Reporting
Extract the minidump from Windows Error Reporting Windows Error reporting has already created a c:\programdata\microsoft\windows\wer minidump of the crash. So one way to find out what went wrong is just to look at the minidump. This
Wer Report
works really well if your application is written in native code and there is no debugger on the machine where the crash occurs. You can use it for managed code too, but you will http://answers.microsoft.com/en-us/windows/forum/windows_vista-files/can-i-deleted-files-in-the-wer-folder/c6dabbce-6295-47f0-80a3-414609c14efd need to use sos.dll to analyze the dump (see MSDN). Open a command prompt (Start->Run, cmd.exe), and switch to your temp directory: C:\Documents and Settings\greggm>cd /d %tmp% Look for the dump file that Windows Error Reporting produced. It will have a ‘.dmp' or ‘.mdmp' extension and the date should be shortly after the crash happened: C:\DOCUME~1\greggm\LOCALS~1\Temp>dir *.*dmpVolume in drive C has no label.Volume Serial Number is 70E3-6676 Directory https://blogs.msdn.microsoft.com/greggm/2007/05/24/debugging-windows-error-reporting/ of C:\DOCUME~1\greggm\LOCALS~1\Temp 05/24/2007 08:54 AM 109,570 4A88835.dmp 1 File(s) 109,570 bytes 0 Dir(s) 25,379,823,616 bytes free Mark the file as read-only. This will prevent Windows Error Reporting from deleting the file after you dismiss the dialog: C:\DOCUME~1\greggm\LOCALS~1\Temp>attrib +r 4A88835.dmp Now dismiss windows error reporting and copy the dump file wherever you want. You can analyze the dump in Visual Studio by opening the dump file as a project (File->Open Project), and start debugging (F5). Strategy #2: Access the dump from Online Crash Analysis Microsoft has a program to allow ISVs to access the crashes in their applications that have been submitted by users. If the person experiencing the crash is a customer, this is a great way to find out what happened. Seethewinqual sitefor more information. Strategy #3: Debug the crash through Just-In-Time DebuggingProbably everyone already knows about this, so I won’t spend much time discussing it. However, as long as the application is crashing on a computer that has a debugger installed, this is the easiest option. The only thing tricky that I will mention is that in Windows Vista, depending on your computers Windows Error Reporting settings, you might actually need to click the ‘Send information' button before Windows Vist
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn http://stackoverflow.com/questions/8764842/where-does-windows-error-reporting-create-the-dump-file more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Where does windows error reporting create the dump file up vote 3 down vote favorite I just want to find out which location does the error reporting WER write its dump file? Also is this location specific to OS? windows windbg windows-error-reporting share|improve this question edited Jun 29 '12 at 7:58 ThinkingStiff 48.1k16109206 asked Jan 6 '12 at 21:36 imak 1,94952665 What is the purpose for? If it is for getting back information MSFT provides a mechanism located here: msdn.microsoft.com/en-us/windows/hardware/gg487440 –Brad Semrad Jan 6 '12 at 21:54 my app keep crashing, i couldn't find much info from dump file windows error reporting i generated from adplus. Just curious if WER dump file has any other info –imak Jan 6 '12 at 22:26 Are you able to debug and see what exceptions are being thrown? –Brad Semrad Jan 6 '12 at 22:34 Like I said i couldn't find much info from that dump file. –imak Jan 6 '12 at 22:39 Not through the dump file but like visual studio and run your code. Are you able to do that? –Brad Semrad Jan 6 '12 at 22:43 add a comment| 1 Answer 1 active oldest votes up vote 7 down vote accepted The documentation for WER says you can set registry setting to control the dump location and the type of dump HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\DumpFolder HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\DumpType share|improve this answer answered Jan 6 '12 at 22:45 jcopenha 3,5671912 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign up using Facebook Sign up using Email and Password Post as a guest Name Email Post as a guest Name Email discard By posting your answer, you agree to the privacy policy and terms of service. Not the answer you're looking for? Browse other questions tagged windows windbg windows-error-reporting or ask your own question. asked 4 years ago viewed 12679 times active 4