Debugging with GDB Manual HP WDB v6.3 (5900-2180, August 2012)
The packcore.tar.Z file can be copied to a different system and the gdb command unpackcore
unpacks the packcore.tar.Z file in the current directory, creating a new packcore directory.
After unpacking the packcore file, the unpackcore command invokes getcore to load the
executable and the core file from the packcore directory, and sets GDB_SHLIB_PATH to the modules
directory in the packcore directory. The modules directory holds all of the shared libraries that
were used when the core file was generated.
The unpackcore command has two optional arguments. The first defaults to packcore.tar.Z
and is the name of the packcore file to be unpacked. The second argument is given if the core file
is too large to fit in the packcore file. It is the path to the core file to be used if the packcore directory
does not contain a core file. If used, this second argument causes a symbolic link to be created in
the packcore directory in place of the missing core file.
The getcore command can be used to examine a packcore directory which was previously
created by unpackcore. It takes one optional argument, the name of the packcore directory, which
defaults to packcore.
14.15.2 Support for the info target Command
The info target command is enhanced to display the memory segments for the corefile. The
output also displays other details, such as system name, node name, operating system release
name, license level, and machine model, for the core file. The enhancement is available for HP-UX
11i v2 and later versions of Itanium systems.
Following is the sample output for the enhanced info target command:
(gdb) file info_target
Reading symbols from info_target...done.
(gdb) core core
Core was generated by `info_target'.
Program terminated with signal 6, Aborted.
#0 0xc00000000032c5b0:0 in kill+0x30 () from /usr/lib/hpux64/libc.so.1
(gdb) info target
Operating System Information:
sysname : HP-UX
nodename : test1
release : B.11.23
version : U (128-user, 256-user or Unlimited-user system)
machine : ia64
idnumber : 0735747273
Symbols from "/tmp/info_target".
Local core dump file:
`/tmp/core',
file type elf64-big.
0x6000000000000000 - 0x6000000000010000 is segment4 (PT_HP_CORE_LOADABLE)
0x9ffffffffb7d9000 - 0x9ffffffffb7da000 is segment5 (PT_HP_CORE_MMF)
0x9ffffffffb7da000 - 0x9ffffffffb7dc000 is segment6 (PT_HP_CORE_MMF)
0x9ffffffffb7dc000 - 0x9ffffffffb7e0000 is segment7 (PT_HP_CORE_MMF)
0x9ffffffffb7e0000 - 0x9ffffffffb7e8000 is segment8 (PT_HP_CORE_MMF)
0x9ffffffffb7e8000 - 0x9ffffffffb7f3000 is segment9 (PT_HP_CORE_MMF)
0x9ffffffffb7f3000 - 0x9ffffffffb7f4000 is segment10 (PT_HP_CORE_MMF)
0x9ffffffffb7f4000 - 0x9ffffffffb7f6000 is segment11 (PT_HP_CORE_MMF)
0x9ffffffffb7f6000 - 0x9ffffffffb7fa000 is segment12 (PT_HP_CORE_MMF)
0x9ffffffffb7fa000 - 0x9ffffffffb7fc000 is segment13 (PT_HP_CORE_MMF)
0x9ffffffffb7fc000 - 0x9ffffffffb7fe000 is segment14 (PT_HP_CORE_MMF)
0x9ffffffffb7fe000 - 0x9ffffffffb7ff000 is segment15 (PT_HP_CORE_MMF)
0x9ffffffffb7ff000 - 0x9ffffffffb800000 is segment16 (PT_HP_CORE_STACK - RSE)
0x9fffffffffffa000 - 0xa000000000000000 is segment17 (PT_HP_CORE_STACK)
0x6000000000000058 - 0x600000000000d000 is heap segment
0x9fffffff7b7f6270 - 0x9fffffff7b7f62e8 is .note.hpux_options in /usr/lib/hpux64/dld.so
0x9fffffff7b7f62e8 - 0x9fffffff7b7f6458 is .dynamic in /usr/lib/hpux64/dld.so
............
...........
154 HP-UX Configuration-Specific Information