execution pattern and translates only the frequently executed code into native Itanium (R)code at runtime.
14.30.1 Debugging the application using GDB under ARIESARIES supports debugging of HP 9000
•Both the GDB and the application run under ARIES.
•No change in GDB user interface (including WDB GUI).
•Negligible loss of performance in interactive mode.
•The HP 9000 GDB is included by default as part of the Integrity
•All GDB commands work just like they would on an HP 9000 server.
Use the following steps to debug HP 9000
1.Set the environment variable PA_DEBUG to 1.
2.Set the environment variable SHELL to point to an HP 9000 shell, copied from an HP 9000
3.Add /usr/ccs/bin to the PATH environment variable.
4.Invoke GDB as:
gdb
After the debugging is finished, perform the following steps:
1.Unset the environment variable PA_DEBUG.
2.Restore the original value of the SHELL environment variable.
3.The rest of the debugging operations are the same as that on the HP 9000
NOTE: Make sure that the user has write permission on /tmp directory and that there is enough space to create a temporary file of one page size as obtained by sysconf(_SC_PAGE_SIZE) system call.
14.30.1.1 Limitations of GDB Support under ARIES
•No support for debuggers other than HP 9000
•No support for old GDB versions (of
•HP 9000 GDB behaves differently for child processes created using fork() and vfork() system calls. ARIES emulates fork() and vfork() system calls
14.30 Debugging with ARIES 231