HP-UX Reference (11i v3 07/02) - 5 Miscellaneous Topics (vol 9)
a
Aries(5)
Itanium(R)-based Systems Only
Aries(5)
ARIES32/64: Core file for PA32/64 application saved to
path/core.PA_application_name
If the emulated PA-RISC application results in a core file named just
core or core.pid, it will be an
Aries core dump and not that of the emulated PA-RISC application.
An Aries-generated PA-RISC HP-UX compatible
core file is recognized by the file command on PA-
RISC and Itanium-based HP-UX machines. See file(1) for more information.
HP-UX 11i Version 3 NOTE:
1. As per the default core file format in HP-UX 11i Version 3 Aries generates PA-RISC application core
file in new format. In the new core file format large utsname structure is written to core file. See
uname(2) for more details on large utsname structure. You need to use latest version of tools like
gdb
which can work with new format core file.
If you want Aries-generated core files to be in old format then use Aries option
-core_format .
Refer to the section ARIES RESOURCE CONFIGURATION FILE: PASSING OPTIONS TO ARIES.
2. If core file pattern and settings have been modified by
coreadm() system call or by init settings -
then Aries does not follow the pattern of writing the corefile to
core. PA-RISC_application_name.
Instead Aries will write core file in the pattern as specified by
coreadm() system call or by
init
settings.
Debugging Aries-Generated PA-RISC Core File on a Different Machine
Debugging Aries-generated PA-RISC core file on different machine (PA-RISC or Itanium-based system) can
be done only with PA-RISC gdb-3.0.01 or later.
Use the following steps to debug an Aries-generated PA-RISC 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-RISC application from the Itanium-
based machine where the core dump file was generated to the target machine.
2. Set the environment variable GDB_SHLIB_PATH
to a colon-separated list of directory path names
where the transferred shared libraries reside.
3. Run
gdb as:
$ gdb PA_application PA_core_file
ARIES RESOURCE CONFIGURATION FILE: PASSING OPTIONS TO ARIES
Options to Aries are passed through a resource configuration file. The Aries resource configuration file
name is one of the following:
• .ariesrc for 32-bit Aries (aries32.so)
• .aries64rc for 64-bit Aries (aries64.so)
Aries Resource Configuration File Format
The Aries resource configuration file may contain multiple lines each of the following format:
<full-path-of-PA-RISC-application1> <aries-options>
<full-path-of-PA-RISC-application2> <aries-options>
...
<full-path-of-PA-RISC-applicationn> <aries-options>
Exception: Instead of the full path of the PA-RISC application, you can specify the root (
/) path. If the
root (/) path is specified, the following options are applied to all PA-RISC applications being executed
through Aries. Specifying the root directory (/) in the first column acts as a wildcard. All PA-RISC appli-
cations will execute under Aries with the Aries options specified after the root (/) path in addition to Aries
options present on lines matching individual application names.
The following rules specify the format of Aries resource configuration files.
1. Separate the application path name and Aries options by white spaces (for example, tab or space).
Multiple instances of white spaces are considered as single white space.
2. Specify the application path name or the root (/) path starting from first column.
3. Specifying an invalid Aries option causes a fatal error and terminates the emulated application.
66 Hewlett-Packard Company − 3 − HP-UX 11i Version 3: February 2007