CRE Programmer's Guide

CRE Service Functions
Common Run-Time Environment (CRE) Programmer’s Guide—528146-004
6-46
CRE_Stacktrace_
The syntax for the TNS environment is:
The syntax for the native CRE environment is:
file_ordinal
if present, identifies an open standard file. If absent, CRE_Stacktrace_ writes trace
information to standard log. You can use the following symbolic names for
file_ordinal:
buffer:buffer_bytes
specifies the address and size of the buffer in which to compose stack trace report
lines. The buffer must be a minimum of 132 characters. CRE_Stacktrace_ uses a
132-byte local buffer if either
buffer or buffer_bytes is not present.
prefix_bytes
if present, requests that each line include a prefix before the generated text. If
absent, or if CRE_Stacktrace_ uses a local buffer, CRE_Stacktrace_ uses zero for
prefix_bytes. prefix_bytes specifies how many bytes of prefix text to use
with each lines of the stack trace:
INT PROC CRE_Stacktrace_( file_ordinal, buffer:buffer_bytes,
prefix_bytes, stack_mark )
EXTENSIBLE;
INT file_ordinal; ! in, optional
STRING .EXT buffer; ! in/out, optional
INT buffer_bytes; ! in, optional
INT prefix_bytes; ! in, optional
INT .stack_mark; ! in, optional TNS only
INT PROC CRE_Stacktrace_( file_ordinal, buffer:buffer_bytes,
prefix_bytes ) EXTENSIBLE;
INT file_ordinal; ! in, optional
STRING .EXT buffer; ! in/out, optional
INT buffer_bytes; ! in, optional
INT prefix_bytes; ! in, optional native only
CRE File Ordinal Symbolic Names
CRE^Standard^Output
CRE^Standard^Log
prefix_bytes
Meaning
< -1
All lines of stack trace include the first prefix_bytes of
buffer:buffer_bytes as prefix text.