HP-UX Programming Tools Release Notes

Chapter 4 33
Problem Descriptions and Fixes
Problems and Limitations
HP PAK Puma Problem Attaching to Program’s First
Child
The Attach to program’s first child option on the Choose target
program for data collection window currently does not work.
A workaround is to use the ps command to learn the process id (pid) of
the child program, and then use the Attach to running program choice
to attach to this pid.
HP PAK Puma X Server Hang During Data Collection
Running HP PAK Puma in graphics mode while collecting performance
data on a graphics-intensive application is likely to hang the X Server.
Use either of the following workarounds:
• Have Puma and the target application use separate displays. Use the
standard X Windows -display option to set either the Puma display
or the target program display.
• Collect the performance data using Puma’s command line interface
and then view the collected data using Puma’s graphical interface.
For example, to collect data from the command line, use the following
commands:
% puma -text
puma> monitor -invoke application-name
HP PAK Puma Limitations with Sampling Timer
• When Wall-Clock timing is selected, Puma can give you information
about both CPU-bound and I/O-bound performance problems.
However, this method of sampling causes Puma to inflate the amount
of time the target process spends in system calls. Therefore, it is best
to be conservative when evaluating the significance of the system call
data.
• When Virtual CPU timing is selected, Puma only gives information
about CPU-bound performance problems. However, this method of
sampling is not biased toward system calls.