dbx provides partial debugging support for optimized code. The extent of the support depends largely upon how you compiled the program.
When analyzing optimized code, you can do the following:
Stop execution at the start of any function (stop in function command)
Evaluate, display, or modify arguments
Evaluate, display, or modify global, local, or static variables
Single-step from one line to another (next or step command)
When programs are compiled with optimization and debugging enabled at the same time (using the –O and –g options), dbx operates in a restricted mode.
The details about which compilers emit which kind of symbolic information under what circumstances is likely to change from release to release.
Source line information is available, but the code for one source line might appear in several different places for an optimized program, so stepping through a program by source line results in the current line being in different places in the source file, depending on how the code was scheduled by the optimizer.
Tail call optimization can result in missing stack frames when the last effective operation in a function is a call to another function.
For OpenMP programs, compiling with the –xopenmp=noopt option instructs the compiler not to apply any optimizations. However, the optimizer still processes the code in order to implement the OpenMP directives, so some of the problems described might occur in programs compiled with –xopenmp=noopt.
Generally, symbolic information for parameters, local variables, and global variables is available for optimized programs. Type information about structs, unions, C++ classes, and the types and names of local variables, global variables, and parameters should be available.
Information about the location of parameters and local variables is sometimes missing for optimized code. If dbx cannot locate a value, it reports that it cannot. Sometimes the value might disappear temporarily, so try to single-step and print again.
The Oracle Developer Studio 12.2 compilers and later Oracle Developer Studio updates for SPARC based systems and x86 based systems provide the information for locating parameters and local variables. Newer versions of the GNU compilers also provide this information.
You can print global variables and assign values to them, although they might have inaccurate values if the final register-to-memory store has not happened yet.
dbx allows you to set breakpoints on inlined functions. Control stops at the first instruction from the inlined function in the caller. You can perform the same dbx operations (for example, step, next, and list commands) on inlined functions as you can perform on non-inlined functions.
The where command shows the call stack with the inlined function and the parameters if location information for the inlined parameters is available.
The up and down commands for moving up and down the call stack are also supported for inlined functions.
Local variables from the caller are not available in the inline frame.
Registers, if shown, are those from the caller's window.
Functions that the compilers might inline include the C++ inline functions, the C functions with the C99 inline keyword, and any other functions that the compiler deems profitable for performance.
The Oracle Developer Studio 12.6: Performance Analyzer contains information that might be helpful when debugging an optimized program.
While most debugging support requires that a program be compiled with -g, dbx still provides the following level of support for code compiled without -g:
Backtrace (dbx where command)
Calling a function but without parameter checking
Checking global variables
Note, however, that dbx cannot display source code unless the code was compiled with the -g option. This restriction also applies to code that has had strip -x applied to it.
For full support, a shared library must also be compiled with the -g option. If you build a program with shared library modules that were not compiled with the -g option, you can still debug the program. However, full dbx support is not possible because the information was not generated for those library modules.
dbx can debug programs that have been completely stripped. These programs contain some information that can be used to debug your program, but only externally visible functions are available. Some runtime checking works on stripped programs or load objects. For example, memory use checking works and access checking works with code stripped with strip -x, but not with code stripped with strip.