HP-UX Reference (11i v2 03/08) - 5 Miscellaneous Topics, 7 Device (Special) Files, 9 General Information, Index (vol 9)

a
Aries(5) Aries(5)
(Itanium(R)-Based Processor Family Only)
3. No support for conditional reporting of system call entry and exit events.
4. No support for old
gdb
versions (of HP-UX 10.20 and earlier). However, debugging HP-UX 10.20
applications using a HP-UX 11.0 PA
gdb is supported.
5. PA
gdb behaves differently for child programs created using
fork() and vfork(). Since in
Aries
vfork() calls made by application are replaced by
fork() calls, the exact behaviour
shown by PA
gdb on PA-RISC/HP-UX platform is not shown by the PA
gdb running under Aries
on HP-UX Itanium-based platform in this case.
6. If the debugged program is hanging in a blocking system call, any attempt to get to the
gdb com-
mand prompt by pressing ˆC will not work. The process has to be killed from outside.
Generation of PA Core File
Aries supports creation of PA core file on Itanium-based system, when the emulated PA application
dumps core.
The size of the core file is limited by
ulimit() or setrlimit() values. See ulimit(2) and
setrlimit (2).
The PA application core file generated by Aries will have the name as
core.PA_application_name
.
HP-UX PA-RISC debuggers are needed to analyze core files generated by Aries for PA applications. For
instance, PA application core file generated by Aries can be debugged using /usr/ccs/bin/gdbpa
on
Itanium-based system. Alternately, the application’s core file can be taken to a PA machine and debugged
using a PA debugger, though it is a very tedious process and likely to be error-prone.
After Aries has successfully written core file for PA application, it will print the following message on
stderr:
ARIES32/64: Core file for PA32/64 application
saved to path/core.PA_application_name
If the emulated PA application results in a core file named just
core or core.
pid, it will be Aries core
dump and not that of the emulated PA application.
Debugging Aries-Generated PA Core File on a Different Machine
Debugging Aries-generated PA core file on different machine (PA or Itanium) can be done only with PA
wdb-3.0.01 or later.
The following steps should be followed to debug Aries-generated PA core file on a machine other than the
one on which the core file was generated.
1. Transfer the core file and all the shared libraries used by the PA application from the Itanium-based
machine where core dump file was generated to the target machine.
2. Set the
GDB_SHLIB_PATH
environment variables to a colon-separated list of directory pathnames
where the transferred shared libraries reside.
3. Run
gdb as:
$ gdb PA_application PA_core_file
Performance-Enhanced Dynamic Translator Beta
1. Introduction
Aries (32-bit -
/usr/lib/hpux32/aries32.so) shipped with HP-UX 11i Version 2.0 is augmented
with the beta version of a performance-enhanced dynamic translator. However this beta translator will
NOT be turned ON by default. This means that the regular usage of Aries will not be affected at all. The
64-bit Aries, /usr/lib/hpux64/aries64.so, does not consist of this beta translator.
2. Usage
In order to turn on the beta translator, the following option string needs to be used in the
.ariesrc file:
-fast_trans
Aries is supposed to run with default options. However, the resource file is a mechanism by which special
options can be supplied to Aries. While starting up a PA application, Aries searches for .aries[64]rc
file in the current directory, then in the user’s home directory and then in the root (/) directory, in that
order. If Aries fails to locate it in any of the three places it uses default options. In the context of the
beta translator, -fast_trans is the special option that needs to be supplied via the .ariesrc file, so
that Aries invokes the beta translator while emulating the given PA application. If no .ariesrc file is
HP-UX 11i Version 2: August 2003 − 2 − Hewlett-Packard Company Section 5−−41