dbxtool - source-level debugger GUI
dbxtool [execfile] [-] [corefile | process-ID ]
[--enable-code-assistance] [--jdkhome path]
[--userdir path] [--fontsize size]
[--locale language[:country[:variant]]]
[--reload path-to-module.jar] [--help]
[--cp:p classpath] [--cp:a classpath]
[--laf LaF-classname ] [--version] [-V]
dbxtool [[-r | -E] 'execfile -arg1 -arg2 ...'] [-]
[corefile | process-ID ] [--enable-code-assistance]
[--jdkhome path] [--userdir path] [--fontsize size]
[--locale language[:country[:variant]]]
[--reload path-to-module.jar] [--help]
[--cp:p classpath] [--cp:a classpath]
[--laf LaF-classname ] [--version] [-V]
Oracle Developer Studio dbxtool is a graphical user interface (GUI) tool that uses the dbx debugger for source-level debugging of programs written in C++, ANSI C, Fortran 77, Fortran 95, and Java programming languages.
If you intend to embed dbxtool in a shell script or driver program, consider using ss_attach (see ss_attach.1 man page) instead.
execfile is an executable file, produced by an Oracle Developer Studio compiler or GNU compiler with the -g option which includes debugging symbols in the execfile or its associated object files.
If you know a process-ID but not the execfile, you can use the - (dash) as the execfile and enter the process-ID option to attach the process to dbxtool.
If a corefile argument is specified, you can use dbxtool to examine the state of the program when the core file was produced.
If you know a corefile name, but not the execfile, you can use the - (dash) as the execfile and dbx will attempt to extract the program name from the core file.
You can specify arguments to be passed to the execfile program only if you specify the -r option or the -E option. You must enclose the execfile and its arguments in single quotes.
Run execfile immediately. Parameters follow the execfile name (including redirection). If the program requires parameters that begin with a dash, the program name and parameters must be enclosed in single quotes. If the program terminates successfully, dbx exits. Otherwise, if a fault occurs, dbx reports the reason and waits for a response.
Parameters follow the execfile name (including redirection). If the program requires parameters that begin with a dash, the program name and parameters must be enclosed in single quotes. If the program terminates successfully, dbx exits. Otherwise, if a fault occurs, dbx reports the reason and waits for a response.
Turn on automatic Code Assistance when launching dbxtool. If you need code assistance support while debugging, specify this option.
Explicitly specifies the path to the JDK. If this option is not given, the command looks for the JDK_HOME environment variable or the JAVA_PATH environment variable to determine a path to the JDK. If neither environment variable is set, the command looks for the JDK in several standard locations.
Explicitly specifies the path to the directory where the tool stores your settings. If this option is not given, the location of your user directory is $HOME/.oracledevstudio/dbxtool-version-operating_system-processor_type.
Sets the font size, expressed in points, in the tool's user interface. If this option is not given, the font size is 11 points.
Uses specified locale information. --reload path-to-module.jar Installs or reinstalls a module JAR file.
Displays the list of command-line options.
Emit the version information. This option is the same as -V.
Emit the version information. This option is the same as --version.
The following options pertain to changing the look and feel of the GUI:
Uses the specified UI class as the tool's look and feel.
Prepends the specified path to the tool's classpath.
Appends the specified path to the tool's classpath.