Capturing a Dump File on a Standalone Device (Windows Embedded CE 6.0)

1/5/2010

By making a simple registry setting, you can use Error Reporting functionality to capture a dump file from a target device that is not connecting to a development workstation. Using this functionality, you can choose the level of detail you need about the target device, and then make the appropriate registry settings that tailor your preference. For example, a System dump includes callstacks and context records for all threads and the contents of the 2048 bytes of memory above and below a faulting thread, while a Complete dump includes the information in a System dump plus the contents of all physical memory.

For more information about the kinds of information captured by different kinds of dump files, see Types of Crash Dump Files.

These options allow you to take advantage of the full range data that can be captured by the error reporting system, even on a standalone device.

To keep a captured dump file on the local machine for debugging

  • To not upload reports but instead keep them on the target device, make the following registry setting:

    [HKEY_LOCAL_MACHINE\System\ErrorReporting\UploadSettings] "DontUpload"=dword:1  
    

See Also

Concepts

Error Reporting Modes and Settings
Error Reporting Overview
Report Upload Client Registry Settings

Other Resources

Post-Mortem Debugging
Report Upload Client