Debug Applications Windows Error Reporting
Contents |
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
Windows Error Reporting Disable
#1: Extract the minidump from Windows Error Reporting Windows Error reporting has already created windows error reporting location a minidump of the crash. So one way to find out what went wrong is just to look at the
Windows Error Reporting Service
minidump. This 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, windows error reporting 1001 but you will 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 windows error reporting logs location is 70E3-6676 Directory 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 c
Studio 2015 products Visual Studio Team Services Visual Studio Code Visual Studio Dev Essentials Office Office Word/Excel/PowerPoint Microsoft Graph
Windows Error Reporting Server 2012
Outlook OneDrive/Sharepoint Skype Services Store Cortana Bing Application Insights Languages windows error reporting delete & platforms Xamarin ASP.NET C++ TypeScript .NET - VB, C#, F# Server Windows Server SQL Server
Windows Vista Error Reporting
BizTalk Server SharePoint Dynamics Programs & communities Students Startups Forums MSDN Subscriber downloads Sign in Search Microsoft Search Hardware Dev Center Hardware Dev Center Explore https://blogs.msdn.microsoft.com/greggm/2007/05/24/debugging-windows-error-reporting/ New device experiences USB driver development Windows IoT Core 3D printing Docs All Windows devices Get started Design Develop Test Customize Manufacture Service Windows drivers Get started with universal Windows drivers Develop, test, and deploy drivers Device and driver development tools Debugging tools for Windows Device and driver technologies Windows driver samples https://msdn.microsoft.com/en-us/library/windows/hardware/dn641144(v=vs.85).aspx Desktop Desktop customizations Enterprise customizations OEM manufacturing guide System builder manufacturing guide Mobile Mobile customizations Mobile deployment and imaging Mobile servicing IoT Core IoT Core manufacturing guide IoT Core updates Downloads Windows Driver Kit (WDK) Hardware Lab Kit (HLK) Assessment and Deployment Kit (ADK) Windows Symbol Packages Windows Debugger (WinDbg) Samples Support Programs Dashboard Explore New device experiences USB driver development Windows IoT Core 3D printing Docs All Windows devices Get started Design Develop Test Customize Manufacture Service Windows drivers Get started with universal Windows drivers Develop, test, and deploy drivers Device and driver development tools Debugging tools for Windows Device and driver technologies Windows driver samples Desktop Desktop customizations Enterprise customizations OEM manufacturing guide System builder manufacturing guide Mobile Mobile customizations Mobile deployment and imaging Mobile servicing IoT Core IoT Core manufacturing guide IoT Core updates Downloads Windows Driver Kit (WDK) Hardware Lab Kit (HLK) Assessment and Deployment Kit (ADK) Windows Symbol Pack
Studio 2015 products Visual Studio Team Services Visual Studio Code Visual Studio Dev Essentials Office Office Word/Excel/PowerPoint Microsoft Graph Outlook OneDrive/Sharepoint Skype Services Store Cortana Bing Application Insights Languages & https://msdn.microsoft.com/en-us/library/windows/desktop/bb513641(v=vs.85).aspx platforms Xamarin ASP.NET C++ TypeScript .NET - VB, C#, F# Server Windows Server SQL Server BizTalk Server SharePoint Dynamics Programs & communities Students Startups Forums MSDN Subscriber downloads Sign in Search Microsoft Search Windows Dev Center Windows Dev Center Explore What’s new for Windows 10 Intro to Universal Windows Platform Coding challenges Develop for accessibility Build for enterprise Windows Store opportunities Docs Windows apps error reporting Get started Design and UI Develop API reference Publish Monetize Promote Games Get started UI design Develop Publish Desktop Get started Design Develop API reference Test and deploy Compatibility Windows IoT Microsoft Edge Windows Holographic Downloads Samples Support Why Windows Dashboard Explore What’s new for Windows 10 Intro to Universal Windows Platform Coding challenges Develop for accessibility Build for enterprise Windows Store opportunities windows error reporting Docs Windows apps Get started Design and UI Develop API reference Publish Monetize Promote Games Get started UI design Develop Publish Desktop Get started Design Develop API reference Test and deploy Compatibility Windows IoT Microsoft Edge Windows Holographic Downloads Samples Support Why Windows Dashboard Develop Desktop technologies Diagnostics Diagnostics Windows Error Reporting Windows Error Reporting Windows Error Reporting Assessment Execution Engine Debugging and authoring support Debugging and Error Handling Hardware Counter Profiling Network Diagnostics Framework Network Monitor Performance Counters Performance Logs and Alerts Process Snapshotting Process Status API (PSAPI) System Event Notification Service System Monitor Tool Help Library Windows Error Reporting What's New in WER About WER Using WER WER Reference Windows Events Windows Performance Toolkit Technical Reference Windows Troubleshooting Platform XAML Diagnostics TOC Collapse the table of content Expand the table of content This documentation is archived and is not being maintained. This documentation is archived and is not being maintained. Windows Error Reporting The error reporting feature enables users to notify Microsoft of application faults, kernel faults, unresponsive applications, and other application specific problems. Microsoft can use the error reporting feature to provide customers with troubleshooting in