Regaining control of wayward threads
The wayward thread
Action if a thread has not returned from a CALL
Regaining control of a thread if the trap has been released
Regaining control of a thread in a continuous loop

The wayward thread
When debugging, a thread can become unsubmissive and wayward in the following ways:-

Action if a thread has not returned from a CALL
Cause the CALL to return by carrying out the awaited action. If waiting in GetMessage, move the mouse over a debuggee window or click on the window. If waiting in a modal dialog, close it. If waiting for something to happen in a thread, cause that thread to "run". Using the hot-key will simulate a message and will cause a return from GetMessage, as will the traffic light control. If you suspect that the reason why the CALL has not returned because it is stuck in a continuous loop, use the hot-key or the traffic light control.

Regaining control of a thread if the trap has been released
Use the hot-key or the traffic light control. In the traffic light control, reduce the action to try to set the trap (F5,F6 or F7 action) and click on "apply". Since GoBug does not know where the running thread is currently executing it floods the code with INT 3, causing an entry into the debug loop, and the thread is then caught. Please note this does not always work!

Regaining control of a thread in a continuous loop
If the current action is F7 then the trap has not been released. Simply pressing F5 or F6 should regain control of the thread. Otherwise, if the trap has been released, use the hot-key or the traffic light control. In the traffic light control, reduce the action to try to set the trap (F5,F6 or F7 action) and click on "apply". Since GoBug does not know where the running thread is currently executing it floods the code with INT 3, causing an entry into the debug loop, and the thread is then caught. Please note this does not always work!