Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Studio 12.3: Debugging a Program With dbx Oracle Solaris Studio 12.3 Information Library |
4. Viewing and Navigating To Code
5. Controlling Program Execution
6. Setting Breakpoints and Traces
8. Evaluating and Displaying Data
11. Debugging Multithreaded Applications
16. Debugging Fortran Using dbx
17. Debugging a Java Application With dbx
18. Debugging at the Machine-Instruction Level
19. Using dbx With the Korn Shell
20. Debugging Shared Libraries
You are depending on macro skimming if you did not compile your code with the -g3 option and have the macro_source dbx environment variable set to skim_unless_compiler or skim.
For skimming to succeed for a module, the following conditions need to be true:
The module must have been compiled with a Oracle Solaris Studio compiler using the -g option.
The compiler used to compile the module must be accessible by dbx.
The source file for the module must be accessible by dbx.
Files included by the source code of the module must be available, i.e., the path given to the -I options when the module was compiled must be accessible by dbx
The source code must be lexically sound. For example, it cannot contain unterminated strings of comments, or be missing #endifs.
If the source code or include files are not accessible by dbx, you can use the pathmap command to make them accessible.