SET_TIMEOUT_BEHAVIOUR Procedure

This procedure tells Probe what to do with the target session when a timeout occurs. [This call is made in the target session.]

Parameters

• behavior - one of the following (see descriptions above):

• retry_on_timeout

• continue_on_timeout

• nodebug_on_timeout

• abort_on_timeout

Exceptions

unimplemented - the requested behavior is not recognized

Usage Notes

The default behavior (if this procedure is not called) is continue_on_timeout, since it allows a debugger client to re-establish control (at the next event) but does not cause the target session to hang indefinitely.

PROCEDURE set_timeout_behavior (behavior IN PLS_INTEGER);

GET_TIMEOUT_BEHAVIOUR - Returns the current timeout behavior. [This call is made in the target session.]

FUNCTION get_timeout_behavior RETURN BINARY_INTEGER;

Information Flags

info_getOerInfo CONSTANT PLS_INTEGER:= 32;

Reasons

reason_oer_breakpoint CONSTANT BINARY_INTEGER:= 26;

RUNTIME_INFO

Runtime_info gives context information about the running program.

Probe v2.4:

Added OER. It gets set if info_getOerInfo is set. The OER is a positive number. It can be translated into SQLCODE by translating 1403 to 100, 6510 to 1, and negating any other value.

TYPE runtime_info IS RECORD 
   ( 
       Line#            BINARY_INTEGER,   (duplicate of program.line#) 
       Terminated       BINARY_INTEGER,   has the program terminated? 
       Breakpoint       BINARY_INTEGER,   breakpoint number 
       StackDepth       BINARY_INTEGER,   number of frames on the stack 
       InterpreterDepth BINARY_INTEGER,   <reserved field> 
       Reason           BINARY_INTEGER,   reason for suspension 
       Program          program_info,     source location 
Following fields were added in Probe v2.4 oer              PLS_INTEGER       OER 
(exception), if any 
   ); 

oer_table

Used by show_breakpoints

TYPE oer_table IS TABLE OF BINARY_INTEGER INDEX BY BINARY_INTEGER;

- SET_OER_BREAKPOINT

Set a breakpoint on an OER. The breakpoint persists for the session (or until deleted), as with code breakpoints.

Parameters

oer - the OER (a 4-byte positive number)

Returns

success

Usage Notes

Less functionality is supported on OER breakpoints than on code breakpoints. In particular, note that:

• No "breakpoint number" is returned - the number of the OER is used instead. Thus it is impossible to set duplicate breakpoints on a given OER (it is a no-op).

• It is not possible to disable an OER breakpoint (although clients are free to simulate this by deleting it).

• OER breakpoints are deleted via delete_oer_breakpoint.

FUNCTION set_oer_breakpoint(oer IN PLS_INTEGER) RETURN PLS_INTEGER;

DELETE_OER_BREAKPOINT

Delete an OER breakpoint.

Parameters

oer - the OER (positive 4-byte number) to delete

Returns

success

error_no_such_breakpt - no such OER breakpoint exists

FUNCTION delete_oer_breakpoint(oer IN PLS_INTEGER) RETURN PLS_INTEGER;

SHOW_BREAKPOINTS

Parameters

• code_breakpoints - indexed table of breakpoint entries, indexed by breakpoint number.

• oer_breakpoints - indexed table of OER breakpoints, indexed by OER.

• PROCEDURE show_breakpoints (code_breakpoints OUT breakpoint_table, oer_breakpoints OUT oer_table);