The HP/DDE install area contains sets of macros that you can
use if you prefer to use dbx
or xdb commands
in place of HP/DDE commands. Additionally, you can enter any dbx
command without using macros if you prefix the command with dbx_.
The following sections detail how to use dbx
or xdb commands
in place of HP/DDE commands.
 |
| |
|
 | NOTE: On Solaris systems, the command files mentioned in the
following sections are found in:/opt/softbench/dde/dde/contrib |
|
|
| |
|
Compatibility with dbx |
|
The debugger provides a set of commands that make dbx
and debugger commands compatible. Compatibility commands for dbx
consist of the prefix dbx_
and standard dbx
syntax. For example, the debugger command break 27
and the compatibility commands dbx_stop at 27
both set a breakpoint at line 27.
The command file /opt/langtools/dde/contrib/dbx_macros
defines macros that let you enter dbx
commands without prefixes. For example, you can specify stop at 27
rather than dbx_stop at 27.
You can read the macros directly into your debugging session with
the following command:
</opt/langtools/dde/contrib/dbx_macros |
Alternatively, you can copy the command into a .dderc
file in your home directory. The debugger automatically reads that
file at startup.
See “Using a Personal Startup File to Customize
the Debugger ” for details
on creating a .dderc
file.
Using the compatibility macros in the dbx_macros
command file masks out some debugger commands. That is, the debugger
executes the macro instead of the debugger command. Debugger commands
that are masked out by macros remain available through the menus.
Prefixing the command with a period (.)
also inhibits macro expansion. For example, the dbx_macros
command file defines a step
macro. You can type .step
to invoke the debugger's step
command rather than the step
macro.
Be aware that the macros affect the input
syntax of commands but have no effect on the way the debugger formats
its output. Debugger command output does not resemble dbx
output.
