| |||
| Home > Associating Threads with Views > Attaching and unattaching windows | |||
If you are licensed to use multiprocessor debugging mode, RealView Debugger Code windows can be attached to specific connections. Similarly, if you are working with an OS-enabled connection, you can attach Code windows to threads.
Be aware that attaching windows to threads does not work in the same way as attaching windows to connections in multiprocessor debugging mode.
The window attachment status is displayed in the Code window title bar:
blank>Specifies that the Code window is not attached to a thread or a connection.
If an OS-aware connection is the current connection, then by default, all unattached Code windows display details of the current thread for that connection. That is, the details of the thread that was most recently running on the target when the target stopped.
[Target]Specifies that the Code window is attached to the OS-aware connection, that is a debug target board or a specified processor on a multiprocessor board. This window displays details of the current thread on that target, if available.
Be aware that, if you later attach the Code window to a thread, and unattach the window from the thread, then the connection is also unattached from that Code window. If the OS-aware connection is not the current connection, then the details of the OS-aware connection are replaced by those of the current connection.
When the Code window is attached to a specific thread, the
thread ID replaces the connection name in the title bar (for example, T0x25520_thread_01.ARM).
If the Code window is attached to the connection, then the connection
status is also replaced.
If you open a new Code window, the attachment of that Code window is inherited from the calling window.
When working with threads, you can change the attachment of your Code window using the thread list.
See also:
the following in the RealView Debugger User Guide: