JDK-8055755 : Information about loaded dynamic libraries is wrong on MacOSX.
  • Type: Bug
  • Component: hotspot
  • Sub-Component: svc
  • Affected Version: 8,9
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: os_x
  • CPU: x86_64
  • Submitted: 2014-08-21
  • Updated: 2018-05-14
  • Resolved: 2014-08-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 7 JDK 8 JDK 9
7u181Fixed 8u172Fixed 9 b31Fixed
Description
The information about loaded dynamic libraries printed in hs_err_pid files or by running the jcmd VM.dynlib is partly incorrect. The address printed in front of the library file name is wrong.
Comments
The issue here is that the addresses for the loaded modules are wrong. Look at the following printout before patch is applied: Dynamic libraries: 0x0000000009ef0000 /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa 0x0000000009ef0000 /System/Library/Frameworks/Security.framework/Versions/A/Security 0x0000000009ef0000 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices ... <snip> 0x0000000009ef0000 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting 0x0000000009ef0000 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print 0x0000000009ef0000 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI All addresses are the same in the above snippet. A view using LLDB will give the following: [ 1] CCD8E6F3-9B17-3B50-9E6A-DE9A081EE440 0x00007fff8a13b000 /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa [ 2] EA03E140-2509-3A07-8440-2DC97C0D478B 0x00007fff94751000 /System/Library/Frameworks/Security.framework/Versions/A/Security [ 3] 3E3F01A8-314D-378F-835E-9CC4F8820031 0x00007fff91add000 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices ...<snip> [161] B3B037D7-1019-31E6-9D17-08E699AF3701 0x00007fff946af000 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting [162] 6065DA3F-7533-3E81-8162-B1D1BED81D54 0x00007fff90455000 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print [163] 18C42525-688C-3D47-B9C9-1E0F8F58FA64 0x00007fff8cd57000 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI And after the patch is applied: Dynamic libraries: 0x00007fff8a13b000 /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa 0x00007fff94751000 /System/Library/Frameworks/Security.framework/Versions/A/Security 0x00007fff91add000 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices ...<snip> 0x00007fff946af000 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting 0x00007fff90455000 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print 0x00007fff8cd57000 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI Now the addresses look more consistent.
27-08-2014