| Debugging a Program With dbx |    
|
| Debugging a Program With dbx |
|
|
Before You Begin |
dbx is an interactive, source-level, command-line debugging tool. Debugging a Program With dbx is intended for programmers with a working knowledge of Fortran, C, or C++, and some understanding of the Solaris
operating environment and UNIX® commands, who want to debug an application using dbx commands.
Debugging a Program With dbx contains the following chapters and appendixes:
Chapter 1 gives you the basics of using dbx to debug an application.
Chapter 2 describes how to start a debugging session, discusses compilation options, and tells you how to save all or part of session and replay it later.
Chapter 3 describes how to set dbx environment variables to customize your debugging environment and how to use the initialization file, .dbxrc, to preserve changes and adjustments from session to session.
Chapter 4 tells you about visiting source files and functions; locating symbols; and looking up variables, members, types, and classes.
Chapter 5 describes how to run, attach to, detach from,. continue execution of, stop, and rerun a program under dbx. It also tells you how to single-step through program code.
Chapter 6 describes how to set, clear, and list breakpoints and traces.
Chapter 7 tells you how to examine the call stack and how to debug a core file.
Chapter 8 shows you how to evaluate data; display the values of expressions, variables, and other data structures; and assign values to variables.
Chapter 9 describes how to use runtime checking to detect memory leak and memory access errors in your program automatically.
Chapter 10 describes the fix and continue feature of dbx that allows you to modify and recompile a source file and continue executing without rebuilding your entire program.
Chapter 11 tells you how to find information about threads.
Chapter 12 describes how to use dbx to debug OpenMP code.
Chapter 13 describes several dbx facilities that help you debug child processes.
Chapter 14 tells you how to use dbx to work with signals.
Chapter 15 describes dbx support of C++ templates, and the commands available for handling C++ exceptions and how dbx handles these exceptions.
Chapter 16 introduces some of the dbx facilities you can use to debug a Fortran program.
Chapter 17 describes how you can use dbx to debug an application that is a mixture of Java code and C JNI (Java Native Interface) code or C++ JNI code.
Chapter 18 tells you how to use event management and execution control command at the machine-instruction level, how to display the contents of memory at specific addresses, and how to display source code lines along with their corresponding machine instructions.
Chapter 19 explains the differences between ksh-88 and dbx commands.
Chapter 20 describes dbx support for program that use dynamically linked, shared libraries.
Appendix A focuses on dbx commands that change your program or its behavior when you run it under dbx.
Appendix B tells you how to manage events, and describes how dbx can perform specific actions when specific events occur in the program you are debugging.
Appendix C gives detailed syntax and functional descriptions of all of the dbx commands.
|
The "pipe" or "bar" symbol separates arguments, only one of which may be chosen. |
|||
|
The colon, like the comma, is sometimes used to separate arguments. |
|||
The compilers and tools and their man pages are not installed into the standard /usr/bin/ and /usr/share/man directories. To access the compilers and tools, you must have your PATH environment variable set correctly (see Accessing the Compilers and Tools). To access the man pages, you must have the your MANPATH environment variable set correctly (see Accessing the Man Pages.).
For more information about the PATH variable, see the csh(1), sh(1), and ksh(1) man pages. For more information about the MANPATH variable, see the man(1) man page. For more information about setting your PATH variable and MANPATH variables to access this release, see the installation guide or your system administrator.
Use the steps below to determine whether you need to change your PATH variable to access the compilers and tools.
|
|
1. Display the current value of the PATH variable by typing the following at a command prompt.
2. Review the output to find a string of paths that contain /opt/SUNWspro/bin/.
If you find the path, your PATH variable is already set to access the compilers and tools. If you do not find the path, set your PATH environment variable by following the instructions in the next procedure.
|
|
1. If you are using the C shell, edit your home .cshrc file. If you are using the Bourne shell or Korn shell, edit your home .profile file.
2. Add the following to your PATH environment variable. If you have Sun ONE Studio software or Forte Developer software installed, add the following path before the paths to those installations.
Use the following steps to determine whether you need to change your MANPATH variable to access the man pages.
|
|
1. Request the dbx man page by typing the following at a command prompt.
If the dbx(1) man page cannot be found or if the man page displayed is not for the current version of the software installed, follow the instructions in the next procedure for setting your MANPATH environment variable.
|
|
1. If you are using the C shell, edit your home .cshrc file. If you are using the Bourne shell or Korn shell, edit your home .profile file.
2. Add the following to your MANPATH environment variable.
The Sun Studio 8 integrated development environment (IDE) provides modules for creating, editing, building, debugging, and analyzing the performance of a C, C++, or Fortran application.
The IDE requires the Core Platform component of Sun Studio 8. You must set the SPRO_NETBEANS_HOME environment variable to the location where the Core Platform component is installed or mounted (installation_directory/netbeans/3.5R) if the Core Platform component is not installed or mounted to one of the following locations:
The command to start the IDE is sunstudio. For details on this command, see the sunstudio(1) man page.
You can access the documentation at the following locations:
If your software is not installed in the /opt directory, ask your system administrator for the equivalent path on your system.
The docs.sun.com web site (http://docs.sun.com) enables you to read, print, and buy Sun Microsystems manuals through the Internet. If you cannot find a manual, see the documentation index that is installed with the software on your local system or network.
The documentation is provided in accessible formats that are readable by assistive technologies for users with disabilities. You can find accessible versions of documentation as described in the following table. If your software is not installed in the /opt directory, ask your system administrator for the equivalent path on your system.
|
HTML at http://docs.sun.com |
|
|
HTML in the installed software through the documentation index at file:/opt/SUNWspro/docs/index.html |
|
|
HTML in the installed software through the documentation index at file:/opt/SUNWspro/docs/index.html |
|
|
HTML at http://docs.sun.com |
The following table describes related documentation that is available at file:/opt/SUNWspro/docs/index.html and http://docs.sun.com. If your software is not installed in the /opt directory, ask your system administrator for the equivalent path on your system.
The following table describes related documentation that is available through the docs.sun.com web site.
Visit http://developers.sun.com/prodtech/cc to find these frequently updated resources:
You can find additional resources for developers at http://developers.sun.com.
If you have technical questions about this product that are not answered in this document, go to:
http://www.sun.com/service/contacting
Sun is interested in improving its documentation and welcomes your comments and suggestions. Email your comments to Sun at this address:
Please include the part number (817-5063-10) of your document in the subject line of your email.
| Debugging a Program With dbx | 817-5063-10 |
|
Copyright © 2004, Sun Microsystems, Inc. All rights reserved.
To Determine Whether You Need to Set Your PATH Environment Variable