02.03.2014 Views

Tornado

Tornado

Tornado

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Tornado</strong> 2.0<br />

User’s Guide<br />

7.2 Starting CrossWind<br />

There are two ways to start a debugging session:<br />

■<br />

From the launcher: Select the desired target and press the button.<br />

■<br />

From the UNIX command line: Invoke crosswind, specifying the target<br />

architecture with the -t option as in the following example.<br />

% crosswind -t sparc &<br />

If you start the debugger from the command line, you must still select a target.<br />

You can either use the Targets menu (see CrossWind Menus, p.238 for details) or<br />

the target wtx command (see Managing Targets, p.257).<br />

7.3 A Sketch of CrossWind<br />

Figure 7-1 illustrates the layout of the main debugger window. This section<br />

discusses each part of the window briefly. The following sections provide more<br />

detail.<br />

The menu bar ➊ provides access to overall control facilities: the File menu lets you<br />

load application modules, or exit; the Targets menu provides a quick way to switch<br />

tasks or targets; the Source menu lets you choose among source-code display<br />

formats; the Tcl menu re-initializes the graphical front end after any customization<br />

to its Tcl definitions; and the Windows menu controls the display of auxiliary<br />

debugger windows. For detailed descriptions of these menus, see CrossWind<br />

Menus, p.238. As usual, the About menu leads to <strong>Tornado</strong> version information, and<br />

the Help menu leads to the <strong>Tornado</strong> online manuals.<br />

The buttons ➋ are the quick path to common debugger commands. Most of them<br />

are grouped into related pairs. Table 7-1 shows a summary of each button’s<br />

purpose. For more detailed descriptions of these buttons, see CrossWind Buttons,<br />

p.244.<br />

The program-display panel ➌ is empty when the debugger begins executing. The<br />

debugger automatically displays the current context here, whenever a command<br />

or an event sets the context. In the case of Figure 7-1, the display is the effect of the<br />

list command, often a useful way to start. Once there is a display in the programdisplay<br />

panel, you can select symbols or lines inside that display to serve as<br />

arguments to the button bar in area ➋.<br />

234

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!