Tornado

7
Debugger
form filename:num (the source file name, a colon, and a line number). For a full
description of linespec formats, see GDB User’s Guide: Printing Source Lines.
search regexp
Displays code centered around the first line (in the current source file) that
contains the regular expression regexp, instead of specifying what line to
display. The command rev is similar, but searches backwards from the current
context. See GDB User’s Guide: Searching Source Files.
break fn
Sets a breakpoint at fn. Instead of first displaying source code, then setting
breakpoints using the graphical interface, you can set a breakpoint directly (if
you know where to go!). The argument fn can be a function name or a line
number. See GDB User’s Guide: Setting Breakpoints.
The break command does not produce a display directly, but sets things up so
that there is at least one place where your program suspends. You can use run
to start the program (except in system mode); when the program suspends at
the breakpoint, the display panel shows the context.
7
Executing Your Program
Just as with the Tornado shell, you can execute any subroutine in your application
from the debugger. Use the following commands:
run routine args
This is the principal command used to begin execution under debugger
control. Execution begins at routine; you can specify an argument list after the
routine name, with the arguments separated by spaces. The argument list may
not contain floating-point or double-precision values. (This command is not
available in system mode; use the shell to get tasks started in that mode. See
5.2.6 Using the Shell for System Mode Debugging, p.170.)
call expr
If a task is already running (and suspended, so that the debugger has control),
you can evaluate any source-language expression (including subroutine calls)
with the call command. This provides a way of exploring the effects of other
subroutines without abandoning the suspended call. Subroutine arguments in
the expression expr may be of any type, including floating point or double
precision.
When you run a routine from the debugger using one of these commands, the
routine runs until it encounters a breakpoint or a signal, or until it completes
execution. The normal practice is to set one or more breakpoints in contexts of
255