Filter
Top Products
n/a
/opt/langtools/
bin
$WDB_ROOT/binlibrtc.sl location
n/a
GDB_SERVER$WDB_ROOT/bin
None
$LIBRTC_SERVER
n/a
$WDB_ROOT/lib/opt/langtools/
bin
NOTE: If you define WDB_ROOT or GDB_ROOT but do not create the correct directory
structure 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 object 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 specified 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 compilation 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,
144 HP-UX Configuration-Specific Information