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
If a child process calls the vfork(2), fork1(2), or fork(2) function, the process id changes, but the process image stays the same. Depending on how the dbx environment variable follow_fork_mode is set, dbx does one of the following.
In the traditional behavior, dbx ignores the fork and follows the parent.
dbx automatically switches to the forked child using the new process ID. All connection to and awareness of the original parent is lost.
This mode is available only when using dbx through the Oracle Solaris Studio IDE or dbxtool.
You are prompted to choose parent, child, both, or stop to investigate whenever dbx detects a fork. If you choose stop, you can examine the state of the program, then type cont to continue; you will be prompted again to select which way to proceed. both is supported only in the Oracle Solaris Studio IDE and dbxtool.