Tornado

7
Debugger
wtx-tool-name
The name supplied for the debugger session to the target server. This is the
name reported in the launcher’s list of tools attached to a target. Default:
crosswind. If you often run multiple debugger sessions, you can use this
parameter to give each session a distinct name.
7.5 System-Mode Debugging
7
By default, in CrossWind you debug only one task at a time. The task is selected
either by using the run command to create a new task, or by using attach to debug
an existing task. When the debugger is attached to a task, debugger commands
affect only that particular task. For example, when a breakpoint is set it applies
only to that task. When the task reaches a breakpoint, only that task stops, not the
entire system. This form of debugging is called task mode.
Tornado also supports an alternate form of debugging, where you can switch
among multiple tasks (also called threads) and even examine execution in system
routines such as ISRs. This alternative mode is called system mode debugging; it is
also sometimes called external mode.
Most of the debugger features described elsewhere in this manual, and the
debugging commands described in GDB User’s Guide, are available regardless of
which debugging mode you select. However, certain debugging commands
(discussed below in 7.5.2 Thread Facilities in System Mode, p.262) are useful only in
system mode.
NOTE: The run command is not available in system mode, because its use of a new
subordinate task is more intrusive in that mode. In system mode, use the shell to
start new tasks as discussed in 5.2.6 Using the Shell for System Mode Debugging,
p.170, then attach to them with the thread command.
7.5.1 Entering System Mode
To debug in system mode, first make sure your debugger session is not attached to
any task (type the command detach, or select Detach from the Targets menu).
Then issue the following command:
261