JDK-8029726 : On OS X some dtrace probe names are mismatched with Solaris
  • Type: Bug
  • Component: hotspot
  • Sub-Component: svc
  • Affected Version: hs24,hs25,7u40,8,8u77,8u101
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2013-12-07
  • Updated: 2016-04-27
  • Resolved: 2013-12-18
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
7u101Fixed 8u101Fixed 9 b02Fixed
Description
thread-probe-start is fired instead of thread-start
thread-probe-stop is fired instead of thread-stop
monitor-probe-waited is fired instead of monitor-waited
Comments
Added 8-bp and 7-bp as the issue affects nightly.
20-11-2015

ILW=MLH=P4, Medium impact as probes are incorrect, dtrace on osx is low likelihood, no workaround.
11-12-2013

I don't know if it is the cause of this mismatch, but MacOS X implements a newer version of dtrace than does Solaris. The define in the code is "USDT2"...
09-12-2013