When the PC Location indication is Running,
your program has control, and you cannot interact with the debugger.
(A small clock animation is also displayed.) Any commands to the
debugger (except commands that restart, kill, or unload your program)
will be queued until your program returns control to the debugger.
Selecting Interrupt Program
will flush any queued commands and return control to the debugger.
If you interrupt your program while it is executing code that
was compiled with the debug options on, you can continue working
just as if you had encountered a breakpoint at that location. A
PC arrow appears in the annotation margin and the source for the
code is displayed. At this point the PC Location shows a valid location
and you can enter debugger commands.
Interrupting in System or Nondebuggable Routines |
 |
If you interrupt the program while it is executing some system-supplied
routine, or while it is executing a routine that was compiled without
debugging information, the PC Location may consist of a virtual
address. The source file display area will be cleared to indicate
that no source is available.
You cannot examine local variables or step through statements.
You can only step by assembly instructions, and examine other procedures
on the call stack.
You can run the nondebuggable routine until it reaches the
point where it returns to its calling procedure by selecting Continue Out.
You can continue doing this until your program returns to debuggable
code. You could also set a breakpoint at some later point in debuggable
code.
If the nondebuggable code is in an infinite loop, or will
not return for some other reason, you must kill or rerun the program.
