Tornado

Tornado 2.0
User’s Guide
(gdb) bt
#0 0x66454 in semBTake ()
#1 0x66980 in semTake ()
#2 0x63a50 in tyRead ()
#3 0x5b07c in iosRead ()
#4 0x5a050 in read ()
#5 0x997a8 in ledRead ()
#6 0x4a144 in execShell ()
#7 0x49fe4 in shell ()
(gdb) thread 3
[Switching to task 0x3aa9d8 tFtpdTask ]
#0 0x66454 in semBTake ()
(gdb) print/x $i0
$3 = 0x3bdb50
As in the display shown above, each time you switch threads the debugger
exhibits the newly current thread’s VxWorks task ID and task name.
Thread-Specific Breakpoints
In system mode, unqualified breakpoints (set with graphical controls on the
program-display window, or in the command panel with the break command and
a single argument) apply globally: any thread stops when it reaches such a
breakpoint. You can also set thread-specific breakpoints, so that only one thread
stops there.
To set a thread-specific breakpoint, append the word thread followed by a thread
ID to the break command. For example:
(gdb) break printf thread 2
Breakpoint 1 at 0x568b8
(gdb) cont
Continuing.
[Switching to task 0x3a4bd8 + tShell ]
Breakpoint 1, 0x568b8 in printf ()
(gdb) i th
8 task 0x3b8ef0 tExcTask 0x9bfd0 in qJobGet ()
7 task 0x3b6580 tLogTask 0x9bfd0 in qJobGet ()
6 task 0x3b15b8 tNetTask 0x66454 in semBTake ()
5 task 0x3ade80 tRlogind 0x66454 in semBTake ()
4 task 0x3abf60 tTelnetd 0x66454 in semBTake ()
3 task 0x3aa9d8 tFtpdTask 0x66454 in semBTake ()
* 2 task 0x3a4bd8 + tShell 0x568b8 in printf ()
1 task 0x398688 tWdbTask 0x66454 in semBTake ()
(gdb) bt
#0 0x568b8 in printf ()
#1 0x4a108 in execShell ()
#2 0x49fe4 in shell ()
264