Options Dialog Box: System Debugger: Verbosity (Compact 2013)
3/26/2014
Use this page of the Options Dialog Box to configure the verbosity settings for the Platform Builder kernel debugger. To display this page, go to Platform Builder > System Debugger > Verbosity in the left pane of the dialog box. The page lists debugger warning messages. Check the boxes next to the messages you want displayed. The following table describes the messages.
Element |
Description |
|---|---|
Warn if breakpoint hit in another thread while stepping |
This message indicates that a breakpoint has been encountered in a thread other than the thread being stepped through. |
Setting breakpoint in delay slot |
This option is supported only for hardware platforms that support delay slots. |
Target exception halt notification |
This message indicates that the device has been halted because an exception occurred. |
Use of data breakpoint emulation |
This message warns the user that data-breakpoint emulation is slow, and might cause the system to appear to be unresponsive. |
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. |
Risk of losing connection |
This message indicates that the connection is unstable. |
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. |
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. |
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. |
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. |
Timestamp of module on device does not match local module |
To avoid debugging with incorrect symbol information, Platform Builder requires the time stamp on the module in the bin file (the target device) and the time stamp on the module in the release directory to match. To determine the time stamps, examine the entry in the Modules Window. |
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. |
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. |
Reset the target device |
This message indicates the user should reset the 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. |
Unable to view threads since process invalid. |
The kernel debugger is unable to find threads for an invalid process. |
Symbols file not found |
This message indicates that the symbols file could not be found, therefore no symbol information is available. |
Attempting to attach to second instance of a .kdmp file |
This message indicates that Windows Embedded Compact Error Reporting is making a second attempt to attach a dump file. |
Do you want to detach from the target |
This message queries whether user wants to detach from the device. |