Capture a Dump File While Debugging (Compact 7)
3/12/2014
You can generate a snapshot of the state of the device in the middle of a debugging session in Platform Builder even if your device hasn’t crashed. In this case, you do not need to include Windows Embedded Compact Error Reporting in your OS design to generate the dump file. After you capture the data, you can save the dump file for later analysis, even when the device is no longer available.
To capture a dump file while debugging, the debugger must be connected and in a break state. Error Reporting captures the state of the device at the point at which the debugger stopped at the breakpoint.
To capture a dump file while debugging
To capture a dump file while debugging in Platform Builder, your program must be in a break state. To place the debugger in a break state when you are debugging, do one of the following.
On the Debug menu, click Break All.
or
Run to a location in the source code by using one of the methods described in Run to a Location.
On the Debug menu, click Capture Dump File.
In the Capture Dump File dialog box, click the type of dump file that you prefer: Context dump, System dump, or Complete dump. For a description of the dump file types, see Choose the Dump File Type.
Click Capture.
In the Save As window, accept the defaults or type a new file name and browse to the location at which you want to save the dump file. The default dump file name is CEDump.kdmp.
Click Save. The Captured dialog box appears and displays the progress of the capture.
In the Captured dialog box, click Close.
For information about how to capture a dump file on a stand-alone device, see Generate a Dump File Automatically, Generate a Dump File from a Process, or Generate a Dump File from a Handled Exception.