HP Caliper for HP-UX Release Notes Release 5.5 (5900-2350, September 2012)

2 Known Problems and Workarounds
GUI Limitations
• Using the same HP Caliper GUI project for both HP-UX and Linux sometimes results in corruption
of the project. When this occurs, the GUI will post an error message at the end of a collection
run saying it failed to save the information to the project. This limitation can be avoided by
using separate workspaces for HP-UX and Linux.
• Running the GUI in native mode (that is, on an Integrity server by means of caliper -g)
can be problematic if the remote system the GUI is displayed on is not on the same LAN as
the server. The most common problems seen are poor responsiveness and no indication of
when a data collection run completes. A workaround is to run the GUI in client mode (that is,
on the remote system). See /opt/caliper/gui_clients/README for details.
• When you try to bring up the GUI's help, you might get the following error if your browser
configuration is not set correctly:
Network Error (tcp_error)
A communication error occurred: "Connection refused"
The Web Server may be down, too busy, or experiencing other problems
preventing it from responding to requests. You may wish to try again at a
later time.
The problem is due to using a proxy and not excluding the localhost. The solution is to add
127.0.0.1 to the proxy exclusion list in your browser's preference settings.
• When you are using an HP Caliper GUI client on a desktop system and the connection with
the Integrity server is severed, the HP Caliper process on the server might not terminate
automatically. If this happens, you need to manually kill the caliper process.
• Running caliper -g and displaying the GUI remotely over slow network lines (such as DSL
connections) can result in the GUI not receiving notification of the completion of data collection.
This results in the GUI behaving as though it is still collecting data, even though the measurement
has completed. This problem is due to a bug in the interaction of Eclipse and Xt.
A workaround is to use a GUI client on the desktop system. For details on installing a client,
see the README file in the gui_clients subdirectory of the HP Caliper home directory. (The
default HP Caliper home directory is /opt/caliper on HP-UX.)
Other Known Problems and Workarounds
• If you are using HP Caliper on HP-UX 11i v2, you will need to install kernel patch PHKL_34020.
Please check the HP IT Resource Center for availability and download information for this
patch.
Contact the HP Caliper team if you have questions about this patch.
• Per-process overview measurement is only available on 11.31 with kernel patch PHKL_38072.
• HP Caliper's measurements may affect your program's performance. Therefore, programs that
make assumptions about the running time of their code might behave differently when run
under HP Caliper.
• When using the pmu_trace measurement, HP Caliper cannot reconcile run-time address
conflicts when your application dynamically loads and unloads modules. HP Caliper displays
the message “The load of the module [library-name] could not be recorded” when a
conflict occurs. The workaround for this problem is not to unload and reload the libraries that
cause a conflict.
• When marking targets of branches in disassembly, targets in split procedures will not be
marked if the branch origin is in one part (hot or cold) of the procedure and branch target is
GUI Limitations 5