HP-UX Linker and Libraries Versions B.11.72 and B.12.57 Release Notes (B2355-91151; September 2011)

in the executable. The HP debugger (WDB) is also enhanced to identify the separate debug
information file during debugging. This feature is useful when you want to ship only the executable
and retain the debug information for later use or to reduce the size of the executable.
A new linker option +dbgfile is introduced to enable this feature. The +dbgfile option takes
a filename as an argument.
The following example shows the result of creating a separate debug information file using the
+dbgfile option.
Example 1 Create a separate debug information file using +dbgfile option
$cc -g example.c -Wl,+dbgfile,a.out.dbg -o a.out
$elfdump -S -h a.out.dbg | grep '\.debug'
31 PBIT 00000000 0000051a 000003fb .debug_macinfo
32 PBIT 00000000 00000915 000000c7 .debug_abbrev
33 PBIT 00000000 000009dc 00000405 .debug_info
34 PBIT 00000000 00000de1 000000df .debug_line
35 PBIT 00000000 00000ec0 00000032 .debug_actual
36 PBIT 00000000 00000ef2 00000030 .debug_procs_abbrev
37 PBIT 00000000 00000f22 0000005b .debug_procs_info
In this example, the name of the separate debug information file is a.out.dbg and it is provided
as the argument to the linker option +dbgfile. This creates a file by name a.out.dbg which
contains all the debug information.
Linker gives out information about the debug file in the executable, and the debugger automatically
picks up the debug information file. As seen through the elfdump output, all the .debug_ sections
are in a.out.dbg file.
This feature is available only on Integrity systems.
Other new options and improvements in linker
A new option +mpas_rotext is provided to enable read-only text segment for MPAS executable.
The kernel patch PHKL_41355 must be installed to make use of this feature.
Linker is enhanced to automatically find linker catalog (ld.cat) in a location relative to linker.
This is in addition to the existing ST_LDCAT environment variable used to point to the catalog file
path.
64-bit pstack tool with new options and improvements
With this release, the pstack tool is 64-bit to handle large executable and core files. A new option
-v is added to the pstack tool to print the version information.
The pstack tool is able to find the executable even if the executable is moved to a different place
during execution. To make use of this feature on NFS, the ONCplus B.11.31.11 must be installed.
To make use of this feature on native filesystem, the VxFS patch PHKL_41728 must be installed on
top of VxFS 5.1.
These enhancements are available only on Integrity systems.
64-bit footprints tool to handle large files
With this release, the footprints tool is 64-bit to handle large object files.
This enhancement is available only on Integrity systems.
New features in this release 5