Viewing Dump Files in Debug Windows (Windows Embedded CE 6.0)
1/5/2010
Windows Embedded CE Error Reporting creates a file association between a crash dump file and the kernel debugger. As a result, when you open a dump file in PB, the IDE can display data from the dump file in the debugger windows. If the debugger finds all the debug symbols, the debugger opens the source window and displays the source line that contains the fault that caused the capture. You can view the corresponding callstack by opening the callstack window.
When the debugger attaches to a dump file, debugger execution control is disabled. Commands such as Run, Go, and Step cannot be performed.
The following table provides more information about the debugger windows that display dump file information:
| Debug window | Description |
|---|---|
Allows you to view the memory contents captured by the Error Reporting system at the time of the second chance exception. If Error Reporting did not capture memory data for a particular address, the memory content for that location displays question marks. You can overwrite any memory location by selecting and entering new values. In this way, you can determine the immediate effect of changing a value. However, if a memory value is changed during the dump file debugging session, it cannot be saved. |
|
Allows you to view the register state captured by the Error Reporting system at the time the fault occurred. Like the memory windows, you can modify the register values during the dump file debugging session to determine the immediate effect, but you cannot save any changes. |
|
Allows you to view the variables and expressions captured by the Error Reporting system at the time the fault occurred. In addition, you can change the display format for watched variables. As with other debugger windows, watch values can be modified but not saved in the original dump file. |
|
Allows you to view a Processes window that contains the data captured in the dump. If the crash dump file comes from a Context dump, the file lists only the faulting process and thread. With system and full dumps, the file shows a list of all processes and threads. |
|
Allows you to view a Threads window that contains the data captured in the dump. If the crash dump file comes from a Context dump, the file lists only the faulting process and thread. With system and full dumps, the file shows a list of all processes and threads. For more information about the types of dump files, see Types of Crash Dump Files. |
|
Allows you to view a Modules window that contains the module data captured in the dump file. The amount of information displayed depends on the type of dump file. |
|
Allows you to view the call stack associated with the fault that caused the dump file to be captured. If you double click on a call stack, the debugger navigates to the source of the call. If debug symbols are not available, the callstack consists of the addresses of the calls. |
See Also
Concepts
Viewing Debug Information in the Debug Windows