PING Procedure

Ping the target session, to prevent it from timing out. Use this procedure when execution is suspended in the target session, for example at a breakpoint.

If the timeout_behavior is set to retry_on_timeout then this procedure is not necessary.

Exceptions

Oracle will display the no_target_program exception if there is no target program or if the target session is not currently waiting for input from the debug session.

PROCEDURE ping;

Timeout Options

Timeout options for the target session are registered with the target session by calling set_timeout_behavior.

• retry_on_timeout - Retry. Timeout has no effect. This is like setting the timeout to an infinitely large value.

• continue_on_timeout - Continue execution, using same event flags.

• nodebug_on_timeout - Turn debug-mode OFF (in other words, call debug_off) and then continue execution. No more events will be generated by this target session unless it is re-initialized by calling debug_on.

• abort_on_timeout - Continue execution, using the abort_execution flag, which should cause the program to abort immediately. The session remains in debug-mode.

retry_on_timeout CONSTANT BINARY_INTEGER:= 0;

continue_on_timeout CONSTANT BINARY_INTEGER:= 1;

nodebug_on_timeout CONSTANT BINARY_INTEGER:= 2;

abort_on_timeout CONSTANT BINARY_INTEGER:= 3;