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 />

this is the same thing as the button. But if there is a function call, the<br />

button executes that function in its entirety, then stops at the line after<br />

the function call.<br />

The display style has the same effect as with the button: thus, the<br />

button steps to either the next machine instruction or the next source<br />

statement, if necessary completing a subroutine call first.<br />

Continues program execution. Click this button to return control to the<br />

task you are debugging, rather than operating it manually from the<br />

debugger after a suspension. If there are no remaining breakpoints,<br />

interrupts, or signals, the task runs to completion.<br />

To continue only until the program reaches a particular line in your<br />

program, drag this icon (using the middle mouse button) from the button<br />

bar to the line in the display panel where the program is to suspend once<br />

more. This has the same effect as dragging the context pointer, but is more<br />

convenient when you scroll the program-display window away from the<br />

current point of suspension.<br />

This button issues the continue command.<br />

Finishes the current subroutine. While stepping through a program, you<br />

may conclude that the problem you are interested in lies in the current<br />

subroutine’s caller, rather than at the stack level where your task is<br />

suspended. Use this button in that situation: execution will continue until<br />

the current subroutine completes, then return control to the debugger in<br />

the calling statement.<br />

This button issues the finish command.<br />

Moves one level up the subroutine stack. The debugger usually has the<br />

same point of view as the executing program: in particular, what variable<br />

definitions are visible depends on the current subroutine. This button<br />

changes the context to the current subroutine’s caller; press it again to get<br />

to that subroutine’s caller, and so on.<br />

This button does not change the location of the program counter; it only<br />

affects what data and symbols are visible to you. If you continue or step<br />

the program, it still takes up where it left off, regardless of whether you<br />

have used this button.<br />

This button issues the up command, and has the same effect on a following<br />

finish or until command as up. The location of the temporary breakpoint<br />

that is set for finish or until depends on the selected frame, which is<br />

changed by up.<br />

248

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

Saved successfully!

Ooh no, something went wrong!