Error Reporting Overview (Windows Embedded CE 6.0)
You can include support for error reporting and select the related Catalog items you want at the time you create an OS design.
Error reporting allows a device to automatically save the state of the machine when a second-chance exception causes a program crash.
The standard error-report format includes extremely useful information for developers, such as the following:
Some system information
A list of loaded modules
Global and local variables
Crash information is compressed into a CAB file and, with user consent, sent to the Microsoft Watson web site. For more information about crash dumps, see Types of Crash Dump Files.
The Watson web server groups crash dump files into categories called buckets that collect crash data with the same code defect. The hit count of a bucket shows how often users encountered the issue that caused the crash. Historically, the worst 1% of problems cause more than half of crashes and hangs that users encounter. For more information about the Error Reporting system of categorizing crash dump files, see Dump File Bucketing.
You can also use Error Reporting functionality to programmatically generate error reports. For more information, see the following topics:
Generating A Dump From A Handled Exception
Provides an example of how to create a special-purpose exception handler.
Capturing a Dump File on a Standalone Device
Describes the registry settings required to keep a crash dump report on a local machine rather than uploading it.
Generating a Dump from a Watched Process
Describes how to capture a dump file based on the operation of a watched process.
Capturing a Dump File While Debugging
Describes how to capture a dump file at any point.
Dump Files in the Kernel Debugger
Provides specific instructions for using the Platform Builder Kernel Debugger to open, save, and view dump files.