C/C++ Programmer's Guide (G06.25+)

Compiler Pragmas
HP C/C++ Programmer’s Guide for NonStop Systems—429301-008
13-82
SAVEABEND
Usage Guidelines
•
The SAVEABEND pragma can appear only on the compiler RUN command line for
native C and C++. On TNS, the pragma can only be specified with the c89
-W[no]saveabend flag.
•
The SAVEABEND attribute is set for native C and C++ programs only if an
executable object file is the output of the compilation. (Process attributes cannot be
set for native relinkable object files.)
•
For TNS programs, the last SAVEABEND or NOSAVEABEND pragma in a translation
unit determines whether or not the system is to create a save file.
•
You can set the SAVEABEND object-file attribute after compilation using the Binder
SET command (for TNS programs) or a linker utility (for native programs).
•
For this option to be effective at run time, the symbolic debugger must be available
on the system on which the process runs.
•
The INSPECT and SAVEABEND pragmas are related:
°
If you specify NOINSPECT, the compiler automatically disables SAVEABEND (as
though you had explicitly specified NOSAVEABEND).
°
If you specify SAVEABEND, the compiler automatically enables the symbolic
debuggers (as though you had explicitly specified INSPECT).
•
The save file contains data area and file-status information at the time of failure.
You can examine the save file during a symbolic debugger session. The symbolic
debugger assigns the save file a name of the form ZZSAnnnn, where nnnn is an
integer. The default names for volume and subvolume are the object file's volume
and subvolume. (You can specify a name for the save file using the symbolic
debugger.) For information on the save file, see the:
°
Inspect Manual
°
Native Inspect Manual