Debugging with GDB (September 2007)

Chapter 14: HP-UX Configuration-Specific Information 191
14.27 Support for ddd
GDB works with ddd, the free GDB GUI shell available at http://mumm.ibr.cs.tu-bs.de/.
While this is not formally supported by Hewlett-Packard, these two do work together.
Note however if you have ddd issues, you’ll need to rep ort them to the ddd support
channel.
14.28 Support for XDB commands
HP WDB provides support for a subset of XDB c omm ands, enabled with the -xdb
option.
14.28.1 stop in/at dbx commands
The commands <stop in function/address> and <stop at line> are equivalent of
dbx <break function/address /line> command. WDB supports the <stop in/at>
command in non-dbx mo de.
For example:
$ gdb a.out (gdb) stop in main Breakpoint 1 at 0x2a34: file list.c, line 18
from /tmp/a.out (gdb) stop at 25 Breakpoint 2 at 0x2a6c: file list.c, line
25 from /tmp/a.out (gdb)
14.29 GNU GDB Logging Commands
The following commands control GDB logging activities:
• set logging file: Set the current log file
• set logging off: Set logging off
• set logging on: Set logging on
• set logging overwrite[on|off]: Set whether logging overwrites or appends to
the log file.
• set logging redirect [on|off]: Set the logging output mode
14.30 Support for command line calls in a stripped
executable
HP WDB enables you to p e rform command line calls in a stripped executable.
14.30.1 Support for command line calls in a stripped
executable on PA-RISC systems
In WDB, to perform command line calls in a shared library without the help of dynamic
linker (using end.o), you must execute the following command: