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.
Windows: Run-time
> Generate Traceback Information
Linux: None
IA-32, IntelŪ EM64T, IntelŪ ItaniumŪ architecture
| Linux: | -traceback -notraceback |
| Windows: | /traceback /notraceback |
None
| OFF | No extra information is generated in the object file to produce traceback information. |
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.
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, 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 Windows systems, when requesting traceback, you must set Enable Incremental Linking in the VS .NET* IDE Linker Options to No. On IA-32 processors, you must also set Omit Frame Pointers (the /Oy option) in the Optimization Options to "No."
On Linux systems, to display the section headers in the image (including the header for the .trace section, if any), use the command:
objlink -h your_app_name.exe
None
Building Applications: Obtaining Traceback Information with TRACEBACKQQ