Developer Guide and Reference

Contents

traceback

Tells the compiler to generate extra information in the object file to provide source file traceback information when a severe error occurs at run time.

Syntax

Linux and macOS:
-traceback
-notraceback
Windows:
/traceback
/notraceback
Arguments
None
Default
notraceback
No extra information is generated in the object file to produce traceback information.
Description
This option tells the compiler to generate extra information in the object file to provide source file traceback information when a severe error occurs at run time.
This is intended for use with C code that is to be linked into a Fortran program.
When the severe error occurs, source file, routine name, and line number correlation information is displayed along with call stack hexadecimal addresses (program counter trace).
Note that when a severe error occurs, advanced users can also locate the cause of the error using a map file and the hexadecimal addresses of the stack displayed when the error occurs.
This option increases the size of the executable program, but has no impact on run-time execution speeds.
It functions independently of the debug option.
On Windows* systems,
traceback
sets the
/Oy-
option, which forces the compiler to use EBP as the stack frame pointer.
On Windows* systems, the linker places the traceback information in the executable image, in a section named ".trace". To see which sections are in an image, use the command:
link -dump -summary your_app_name.exe
To see more detailed information, use the command:
link -dump -headers your_app_name.exe
On Linux* systems, to display the section headers in the image (including the header for the .trace section, if any), use the command:
objdump -h your_app_name.exe
On
macOS*
systems, to display the section headers in the image, use the command:
otool -l your_app_name.exe