Programming Guide : Debugging Your Application : How You Can Monitor a Running Application : Thread Map
 
Share this page          
Thread Map
The Thread Map portlet on the Monitor tab provides a visual representation of the current application threads and their relationships. Each rectangular node on the tree represents one thread. The lines connecting the nodes show the parent-child relationships, with the parent displayed above its children. If a frame was opened with an openframe statement that set the parent frame to null, the word NULL appears as the parent.
For each node, OpenROAD provides the following information about the thread it represents:
Thread identifier
Tells you which frame began the thread (for example, main_control:1). The number after the starting frame's name indicates when, in relation to other threads, the thread began. For example, if the number is 3, that thread is the third thread started in the application.
Name of the currently active executable component of the thread
Displays the name of the current frame, procedure, or user class method in parentheses
Status of the thread
Is displayed in the third line of the rectangle representing the thread
You can access the following options from the pop-up menu that appears when you right-click any thread box in the tree structure:
Call Stack
Displays the thread's detailed call stack.
For information about using the call stack, see Call Stack Window.
Event Queue
Displays the event queue for the thread's current frame.
For information about using the event queue, see Event Queue Window.
Debugger Window
Displays the window for the thread's current frame.
For information about this window, see How You Can Use the Debugger Window.