Debugging with GDB (February 2008)
Table Of Contents
- Summary of GDB
- A Sample GDB Session
- Getting In and Out of GDB
- GDB Commands
- Running Programs Under GDB
- Stopping and Continuing
- Examining the Stack
- Examining Source Files
- Examining Data
- Using GDB with Different Languages
- Examining the Symbol Table
- Altering Execution
- GDB Files
- Specifying a Debugging Target
- HP-UX Configuration-Specific Information
- Summary of HP Enhancements to GDB
- HP-UX dependencies
- Supported Platforms and Modes
- HP-UX targets
- Support for Alternate root
- Specifying object file directories
- Fix and continue debugging
- Inline Support
- Debugging Macros
- Debugging Memory Problems
- When to suspect a memory leak
- Memory debugging restrictions
- Memory Debugging Methodologies
- Debugging Memory in Interactive Mode
- Debugging Memory in Batch Mode
- Debugging Memory Interactively After Attaching to a Running Process
- Configuring memory debugging settings
- Scenarios in memory debugging
- Stop when freeing unallocated or deallocated blocks
- Stop when freeing a block if bad writes occurred outside block boundary
- Stop when a specified block address is allocated or deallocated
- Scramble previous memory contents at malloc/free calls
- Detect dangling pointers and dangling blocks
- Detect in-block corruption of freed blocks
- Specify the amount of guard bytes for every block of allocated memory
- Comparison of Memory Debugging Commands in Interactive Mode and Batch Mode
- Heap Profiling
- Memory Checking Analysis for User Defined Memory Management Routines
- Commands to track the change in data segment value
- Thread Debugging Support
- Debugging MPI Programs
- Debugging multiple processes ( programs with fork and vfork calls)
- Debugging Core Files
- Printing the Execution Path Entries for the Current Frame or Thread
- Invoking GDB Before a Program Aborts
- Aborting a Command Line Call
- Instruction Level Stepping
- Enhanced support for watchpoints and breakpoints
- Debugging support for shared libraries
- Language support
- Enhanced Java Debugging Support
- Commands for Examining Java Virtual Machine(JVM) internals
- Support for stack traces in Java, C, and C++ programs
- Support for 64-bit Java, C, aC++ stack unwinding
- Enhanced support for C++ templates
- Support for __fpreg data type on IPF
- Support for _Complex variables in HP C
- Support for debugging namespaces
- Command for evaluating the address of an expression
- Viewing Wide Character Strings
- Support for output logging
- Getting information from a non-debug executable
- Debugging optimized code
- Visual Interface for WDB
- Starting and stopping Visual Interface for WDB
- Navigating the Visual Interface for WDB display
- Specifying foreground and background colors
- Using the X-window graphical interface
- Using the TUI mode
- Changing the size of the source or debugger pane
- Using commands to browse through source files
- Loading source files
- Editing source files
- Editing the command line and command-line history
- Saving the contents of a debugging session to a file
- Support for ddd
- Support for XDB commands
- GNU GDB Logging Commands
- Support for command line calls in a stripped executable
- Displaying the current block scope information
- Linux support
- The HP-UX Terminal User Interface
- XDB to WDB Transition Guide
- By-function lists of XDB commands and HP WDB equivalents
- Overall breakpoint commands
- XDB data formats and HP WDB equivalents
- XDB location syntax and HP WDB equivalents
- XDB special language operators and HP WDB equivalents
- XDB special variables and HP WDB equivalents
- XDB variable identifiers and HP WDB equivalents
- Alphabetical lists of XDB commands and HP WDB equivalents
- Controlling GDB
- Canned Sequences of Commands
- Using GDB under gnu Emacs
- GDB Annotations
- The gdb/mi Interface
- Function and purpose
- Notation and terminology
- gdb/mi Command Syntax
- gdb/mi compatibility with CLI
- gdb/mi output records
- gdb/mi command description format
- gdb/mi breakpoint table commands
- gdb/mi Data manipulation
- gdb/mi program control
- Miscellaneous GDB commands in gdb/mi
- gdb/mi Stack Manipulation Commands
- gdb/mi Symbol query commands
- gdb/mi Target Manipulation Commands
- gdb/mi thread commands
- gdb/mi tracepoint commands
- gdb/mi variable objects
- Reporting Bugs in GDB
- Installing GDB
- Index
Chapter 14: HP-UX Configuration-Specific Information 119
If you specify both WDB_ROOT and GDB_ROOT, the value for GDB_ROOT is ignored.
HP WDB supports these environment variables to override the location of different
component of HP WDB.
Defined Variable WDB Location GDB location librtc.sl location
None /opt/langtools/bin /opt/langtools/bin /opt/langtools/lib
WDB_ROOT $WDB_ROOT/bin $WDB_ROOT/bin $WDB_ROOT/lib
GDB_ROOT n/a $GDB_ROOT/bin /opt/langtools/bin
GDB_SERVER n/a $GDB_SERVER n/a
LIBRTC_SERVER n/a n/a $LIBRTC_SERVER
Note: If you define WDB_ROOT or GDB_ROOT but do not create the correct directory struc-
ture below it, the debugger may fail.
14.6 Specifying object file directories
GDB enables automatic loading of debug information from object modules when an
application is compiled with the +objdebug option.
GDB uses the full path name to the object module files and searches the same directories
for source files.
Although this behavior is transparent, you can control when and how object files are
loaded with three commands:
objectdir path
Specifies a colon (:) separated list of directories in which GDB searches for ob-
ject files. These directories are added to the beginning of the existing objectdir
path. If you specify a directory that is already in the objectdir path, the spec-
ified directory is moved up in the objectdir path so that it is searched earlier.
GDB recognizes two special directory names: $cdir, which refers to the com-
pilation directory (if available) and $cwd, which tracks GDB’s current working
directory.
objectload file.c
Causes GDB to load the debug information for file.c immediately. The default
is to load debug information from object modules on demand.
objectretry file.c
Forces GDB to retry loading an object file if GDB encounters a file error while
reading an object module. File errors that might cause this include incorrect
permissions, file not found, or if the objectdir path changes. By default, GDB
does not try to read an object file after an error.
pathmap
Enables you to define a list of substitution rules to be applied to path names to
identify object files and the corresponding source files. The pathmap command,
however, may not find source files if the object files are not available.
This minimizes or eliminates the need to specify multiple objectdir commands
when object files are moved from the compilation directories or when compila-
tion directories are mounted over NFS.