RealView® Debugger RTOS Guide 6.7. Interaction of OS resources and RealView Debugger

6.7. Interaction of OS resources and RealView Debugger

Be aware of the following interactions between OS resources and RealView Debugger:

The thread status, as shown in the Resource Viewer pane, is fully integrated with the thread list as shown in the Code window.
OS resource actions and target execution control are independent. Using actions to suspend or resume threads is independent of thread control in RealView Debugger:
- If you suspend a specific thread, that thread is not captive in the debugger. The Resource Viewer pane shows the thread as suspended, but the Code window does not show that the thread has stopped, that is, it is shown as running in the Registers pane or in the Call Stack pane.
- If you resume a captive thread, the Resource Viewer pane shows the thread as running, but the debugger still believes that it has the thread captive. To update the debugger state, you must disconnect and then reconnect.
- If you stop a thread from the Code window, using an action to resume does not show the thread as running, that is it still appears to be stopped.

Copyright © 2006, 2007 ARM Limited. All rights reserved.	ARM DUI 0323B
Non-Confidential
PDF version