JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris Studio 12.3: Debugging a Program With dbx     Oracle Solaris Studio 12.3 Information Library
search filter icon
search icon

Document Information


1.  Getting Started With dbx

2.  Starting dbx

3.  Customizing dbx

4.  Viewing and Navigating To Code

5.  Controlling Program Execution

6.  Setting Breakpoints and Traces

7.  Using the Call Stack

8.  Evaluating and Displaying Data

9.  Using Runtime Checking

10.  Fixing and Continuing

11.  Debugging Multithreaded Applications

12.  Debugging Child Processes

13.  Debugging OpenMP Programs

14.  Working With Signals

15.  Debugging C++ With dbx

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

A.  Modifying a Program State

B.  Event Management

C.  Macros

Macro Expansion

Macro Definitions

Compiler and Compiler Options

Tradeoffs in Functionality


Skimming Errors

Using the pathmap Command To Improve Skimming

D.  Command Reference


Skimming Errors

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:

If the source code or include files are not accessible by dbx, you can use the pathmap command to make them accessible.