29
TIDE and Tibbo BASIC User Manual
©2000-2008 Tibbo Technology Inc.
Pause: This message occurs when the Virtual Machine on the
target was stopped while not executing code (in other words,
it was caught between events). No program pointer is
displayed in this state, because no code is being executed.
You can check and modify the state of properties and global
variables, etc using the watch. This state is entered by
selecting Debug > Pause.
Abort (exception): This message indicates that an internal
error has occurred. The message in parentheses is a short
error code. If you hover your mouse over it, you will see a
more detailed report of the error. The program pointer will
appear at the problematic line. This state is similar to a
break, only it is not caused by a breakpoint but by an
abnormal condition. All possible causes for exception are
listed in
.
Communication States
While TIDE is in communication with the target, the status bar displays a moving
indicator of the communication state.
Communication in progress: The circle is green, and moves
from side to side. It advances one step whenever TIDE gets a
reply to a debug command.
Communication problem: The circle is yellow, and does not
move. This state means TIDE did not receive any reply to debug
commands for more than 6 seconds. The program may be still
running on the target.
No Communication: The circle is red, and does not move.
Occurs when TIDE did not receive any reply to debug
commands for more than 12 seconds. The program may be still
running on the target.
Exceptions
Exceptions are "emergency" halts of program execution. Exceptions are generated
when the Virtual Machine encounters something that really prevents it from
continuing normal operation. When exception happens you see "ABORT" target
state in the status bar, like this:
"(DIV0)" is an abbreviated problem description. Hover the mouse over this and you
will get a more detailed description.
Listed below are all possible exceptions. When you are in the
mode any
exception from the list below causes the Virtual Machine to abort execution. In the
mode, some "lesser" problems do not cause the halt. The logic here is
that there will probably be nobody to restart the problem or check what happened
anyway, so the Virtual Machine just tries to continue operation.
Cod
e
Description
Halt in
debug
mode?
Halt in
release
mode?
29
27
27