Options Dialog Box: System Debugger Verbosity (Windows Embedded CE 6.0)
1/6/2010
This dialog box enables you to configure the verbosity settings for the Platform Builder kernel debugger.
The options on this dialog box indicate a variety of warning messages that the kernel debugger can display. To display a particular warning message, check the box next to the message you want displayed.
The following list shows the available warning messages that the kernel debugger can display.
| Element | Description |
|---|---|
Source file not found |
The kernel debugger could not locate the source file. You might need to modify the source-file mapping. For more information, see Find Source Dialog Box. |
Timestamp of module on device does not match local module |
To avoid debugging with incorrect symbol information, Platform Builder requires the timestamp on the module in the bin file (the target device) and the timestamp on the module in the release directory to match. To determine the timestamps, examine the entry in the Modules Window. |
Local copy of executable file was not found |
The kernel debugger could not locate the source file. You might need to modify the source file mapping. For more information, see Setting the Source Path Mapping. |
ARM floating point exception imprecise |
This warning indicates that a floating-point exception from the ARM Vector Floating Point coprocessor has appeared. The exception is caused by an earlier instruction. It appears when the result of the instruction that caused the exception is used. |
Debug stop without disabling KdStub |
A debug stop command was issued, but KdStub is still attached to the process. |
Unable to view threads since process invalid |
The kernel debugger is unable to find threads for an invalid process. |
Pass exception on to the program being debugged |
This message asks the user if a first-chance exception should be passed to the thread that caused the exception. |
Breakpoint moved to next line |
The kernel debugger moved the indicated breakpoint to the next line of code. |
Breakpoint detected in unmapped source file |
The kernel debugger detected a breakpoint in an unmapped source-code file. To continue, either delete the breakpoint, or create a source-path mapping. For more information, see Setting the Source Path Mapping. |
Insufficient RAM pages for ROM breakpoints |
To support ROM breakpoints, the debugger creates a mirror of ROM pages in RAM. This warning indicates that the available RAM pages are insufficient to create this mirror. For more information, see Adding Support for ROM Breakpoints. |
Unable to remap address to RAM for ROM breakpoint |
Platform Builder was unable to create a mirror of the indicated ROM breakpoint at an available RAM address. |
Range stepping may fail due to lack of ROM breakpoints |
Because range stepping requires multiple RAM pages, there might not be enough RAM pages allocated to successfully range step. |
Unknown error setting breakpoint on device |
Platform Builder was unable to set the requested breakpoint due to an unknown error. |
Setting breakpoint in delay slot |
This option is supported only for hardware platforms that support delay slots. This message warns the user that setting a breakpoint in a delay slot might alter the order of program execution. |
Use of data breakpoint emulation |
This message warns the user that data-breakpoint emulation is slow, and might cause the system to appear to unresponsive. |
Target exception halt notification |
This message indicates that the target device has been halted because an exception occurred. |
Attempting to attach to second instance of a .kdmp file |
This message indicates that Windows Embedded CE Error Reporting is making a second attempt to attach a dump file. |
Reset the target device |
This message indicates the user should reset the target device. |
Target Control communication has timed out |
This message indicates that the Target Control service is unable to complete requested communication within the allotted time. |
Risk of losing connection |
This message indicates that the connection is unstable. |
See Also
Reference
Options Dialog Box: System Debugger
Options Dialog Box (Visual Studio)