#handle:do: contexts, and some of
the processes startup contexts).
The default mode for new debuggers can be changed in the launchers "source & debugger" settings menu.
You can resume execution of the stopped method, by pressing the "continue" button.
A quick terminated process has no chance to perform any cleanup actions;
not even unwind blocks are evaluated.
If you quick terminate a views process,
chances are high that inoperative views are left on the display, cursors
are not restored or semaphores stay blocked (all of this is cleaned up
by unwind handlers, if properly terminated).
You can get rid of remaining views with the launchers "destroy view"
utility function (which you may have to perform multiple times,
to destroy all intermediate views up to the topview - try to click on an
outer view, if possible).
Blocked semaphores have to be released manually, by
opening a debugger on a blocking process and evaluating "self signal"
in a context where that semaphore is the receiver.
The same applies to any critical regions which have been entered at termination time.