prev up next

Button functions

The most common functions are available in a row of buttons (they are also available in the menu):

Continue
Continue execution
The process continues execution where it was stopped originally.

Abort
Abort the current activity (if possible)
This function simply raises the AbortSignal, which is cought by most processes at some save place.
For example, workspaces catch this signal while executing a 'doIt' expression; the fileBrowser while filing in code, and the event dispatcher when processing an event.
Pressing 'Abort' will therefore break out and return to this save place. (thus abort a doIt-evaluation or the processing of the current event).

Typically, this is equivalent to a resume of the corresponding handler contexts sender.

Most often, this is the recommended button to press, in order to exit the debugger after an error has been encountered,

Terminate
Terminate the erronous process.
This is a soft terminate, in that the process gets a chance to perform its cleanup actions (see ``stack unwinding and signal handling''). If the process is controlling a view (i.e. a windowGroup process), all of its windows are closed.
This function is disabled in a modal debugger (because this would terminate the event dispatcher or scheduler).

Report By Mail
Send an email to exept.
If this error persists, and it is not an error which results from an invalid configuration or from bad input, you may want to press this button to send an email notification to the Smalltalk/X maintenance group at exept.
The dialog allows you to enter additional information or a friendly hello-message to the mails bodytext, and also to adjust any sender information. When you click on the send button there, an email providing stack-walkback info is sent to exept.
Next
Single step for next sourceline
Let the process continue execution, until the current source line changes in the selected context. Due to the implementation, single stepping may be a bit slow, if many computations are done in called methods.
This function is not available for inspecting debuggers.

Step
Single step for send in this method
Let the process continue execution, until the next message send is performed in the selected context. Due to the implementation, single stepping may be a bit slow, if many computations are done in called methods.
This function is not available for inspecting debuggers.

Send
Single send
Let the process continue execution for one message send - showing every message send.
This function is not available for inspecting debuggers.

Return
Return from this method
continue execution as if the selected context returned - effectively "jumping out" and returning from this context (i.e. simulate a '^ nil' from the selected context).
If there is a selection in the codeview, which forms a valid expression, that value is used as return value. Otherwise the method returns nil to its sender.

In the current ST/X implementation, this function cannot be performed on block contexts or on contexts of methods which have been compiled with certain compiler-optimizations enabled.
The Return-Button is deisabled if such a context is selected.

Restart
Restart this method
continue execution by restarting the selected context.

In the current ST/X implementation, this function cannot be performed on block contexts or on contexts of methods which have been compiled with certain compiler-optimizations enabled.
The Restart-Button is deisabled if such a context is selected.


Doc $Revision: 1.11 $ $Date: 2009/10/26 11:04:02 $