JDK-7010732 : SA_ALTROOT only works if running the SA tools from their build directory.
  • Type: Bug
  • Component: hotspot
  • Sub-Component: svc
  • Affected Version: 6
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: solaris
  • CPU: generic
  • Submitted: 2011-01-06
  • Updated: 2014-05-27
  • Resolved: 2014-01-28
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 9
9 b03Fixed
Related Reports
Relates :  
JDK-7009089 - SA SA_ALTROOT may not work properly
Relates :  
JDK-7127191 - SA JSDB does not display native symbols correctly for transported Linux cores
Description
Using Serviceability Agent tools with the SA_ALTROOT environment variable only works if running the SA tools from their build directory.

Two problems:

The packager script "mkinstall" does not copy the libsaproc_audit.so library.

The saenv.sh and saenv64.sh scripts assume that the same library is to be found in a relative path (in the build directory).


e.g.
Build the SA tools, run "sh mkinstall" to create an sa17.tar.gz.  Take this bundle where it is needed, and unpack.  Then:

$ ./clhsdbproc64.sh executable corefile
SA_ALTROOT is set and can't find libsaproc_audit.so.
Make sure to build it with 'make natives'.
Comments
It's solaris sparcv9 specific issue. Linux doesn't build libsaproc_audit.so
17-01-2014
EVALUATION Changes required to the mkinstall, saenv.sh and saenv64.sh scripts.
06-01-2011