How you start dbx depends on what you are debugging, where you are, what you need dbx to do, how familiar you are with dbx, and whether you have set up any dbxenv variables.
You can use dbx entirely from the command line in a terminal window, or run dbxtool , a graphical user interface for dbx. For information about dbxtool, see the dbxtool man page and the online help in dbxtool.
The simplest way to start a dbx session is to type the dbx command or dbxtool command at a shell prompt.
To start dbx from a shell and load a program to be debugged, type:
$ dbx program-name
or
$ dbxtool program-name
To start dbx and load a program that is a mixture of Java code and C JNI code or C++ JNI code:
$ dbx program_name{.class | .jar}
The Oracle Solaris Studio software includes two dbx binaries: a 32-bit dbx that can debug 32-bit programs only and a 64-bit dbx that can debug both 32-bit and 64-bit programs. When you start dbx, it determines which of its binaries to execute. On 64-bit operating systems, the 64-bit dbx is the default.
When using the 32-bit dbx on a 64-bit Linux OS, do not use the debug command or set the follow_fork_mode environment variable to child if the result will be execution of a 64-bit program. Exit dbx and start the 64-bit dbx to debug a 64-bit program.
For more information about the dbx command and startup options, see dbx Command and the dbx(1) man page.