To save a session to a file:

1.Right-click an empty region of the source or debugger pane.

2.Choose "Save Session to vdb.pid" from the pop-up menu.

The debugger writes the input and output to a file whose name ends in the pid of the debugger. If you save the session more than once, the new transactions are appended to the file.

14.32 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 report them to the ddd support channel.

14.33 Support for XDB commands

HP WDB provides support for a subset of XDB commands, enabled with the -xdb option.

14.33.1stop 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 mode.

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.34 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[onoff]: Set whether logging overwrites or appends to the log file.

set logging redirect [onoff]: Set the logging output mode

14.35Support for command line calls in a stripped executable

HP WDB enables you to perform command line calls in a stripped executable.

238 HP-UX Configuration-Specific Information

Page 238
Image 238
HP gnu source-level debugger 5992-4701 manual Support for ddd, Support for XDB commands, GNU GDB Logging Commands