aries.5 (2010 09)

ARIES(5) ARIES(5)

(HP Integrity Systems Only)

4. ARIES does not guarantee correct emulation of PA-RISC applications which make assumptions about

"time taken to execute certain parts of application code and/or system calls". Such applications are

theoretically non-synchronized applications, and hence, need to be corrected with proper synchroni-

zation techniques using mutex locks and/or semaphores.

5. ARIES does not support applications that use

ptrace() or profil() system calls. However,

ARIES supports debugging of emulated applications using PA-RISC

gdb. Refer to the PA-RISC

HP-UX GDB DEBUGGING SUPPORT section in this manpage for more information.

6. ARIES consumes a small amount of memory from the emulated application’s virtual memory address

space. Therefore ARIES does not support applications that are nearly or completely maxed out on

their virtual address space usage in data segment.

7. ARIES does not support applications that rely on differences between

fork() and vfork() system

calls. However, most applications that use the

vfork() system call do use it with a purpose which

is well known to the programmer. It is an extremely rare condition that a standard application

would have any such reliance on the differences between fork() and vfork() system calls. See

vfork (2) and fork (2) for details.

8. ARIES returns information pertinent to a PA-RISC 2.0 processor, for certain system calls. For

instance, a call made to

sysconf(), with

_SC_CPU_VERSION, will return

CPU_PA_RISC2_0.If

the application requires that it be able to determine that it is running on an Integrity system, then it

should use the

system() call and the Integrity native command getconf() to get the required

ﬁelds. See sysconf (2), system (3S), and getconf (1) for more information.

AUTHOR

ARIES was developed by HP.