Guardian Programming Reference Summary for pTAL and TAL

Procedure Calls Summary (G-N)
Guardian Programming Reference Summary for pTAL and TAL—522631-001
6-14
The displayed context is affected when any of the following bits are set to 1:
-7 HIST_INIT_ERROR
An error occurred during an attempt to initialize the stack trace.
-8 HIST_ERROR
The stack tracing mechanism failed while attempting to trace back to the calling
procedure.
-11 HIST_MISSING_HOOK
This error is not returned in the D40 release.
workspace, INT.EXT:ref:(HIST_WORKSPACE_TEMPLATE) input, output
version, INT(32):value input
options, INT:value input
<13:15> =0 HO_Init_Here
starts a trace of the current stack with the context of this call to
HIST_INIT_. The context parameter is ignored in this case.
1 HO_Init_uContext
uses the uContext structure whose address is passed in the context
parameter. A uContext structure is a structure of type UCONTEXT_T that is
passed to a signal handler installed by the SIGACTION_INIT_ or
SIGACTION_SUPPLANT_ procedure. HIST_INIT_ initializes the trace at
the point where the signal was generated. See “Protected contexts” under
“Considerations” for more information.
2 HO_Init_JmpBuf
uses the context saved in a TNS/R native jump buffer to start tracing at the
point of a call to the SETJMP_ or SIGSETJMP_ procedure that filled the
jump buffer. The address of the buffer is passed to HIST_INIT_ in the
context parameter.
3 HO_Init_31Regs
is reserved for Tandem use.
4 HO_Init_Address
uses a 32-bit TNS/R native address for the context. This address is passed to
the HIST_INIT_ procedure in the context parameter. A subsequent call to
HIST_FORMAT_ returns context for that location. The address must point
to a code location, but that location can contain TNS instructions or RISC
instructions. To find out what is at a TNS address, you must first convert the
TNS address into a RISC address. See the NonStop Himalaya
K10000/K20000 Server Description Manual for details on address
translation.