First, welcome to DTrace: I think you'll enjoy the ride.
Since the hotspot provider is a USDT (User Statically Defined Tracing)
provider, the provider name is going to be hotspot1234, 1234 is the PID
of the JVM process. The probes don't get created until the JVM is
running, and they go away when the JVM exits.
And just in case this question comes up, some of probes that tend to
fire very often require the -XX:+ExtendedDTraceProbes JVM option to be
In you haven't seen it, see
what I believe is the official documentation for the hotspot probes.
Keep in mind that even though the documentation show the "args" array
being used, USDT probes don't support the args array. You have to use
the built-in variables, arg0, arg1, etc.
Sent: Monday, December 15, 2008 11:22 AM
Subject: [dtrace-discuss] No hotspot probes available?
I'm new to DTrace; been working through the "Solaris Performance and
Tools" book this morning. DTrace is working great, I've learned some
interesting things, and have run a number of the DTrace Toolkit
and written a few tiny ones.
However, I can't get any of the hotspot probes to work. DTrace
no probes that match hotspot. I'm running the OpenSolaris 11/08
release, using the default java (which is 1.6.10).
56144 279580 4262222
ID PROVIDER MODULE FUNCTION NAME
dtrace: failed to match hotspot*:::: No probe matches description
java version "1.6.0_10"
Java(TM) Platform, Standard Edition for Business (build 1.6.0_10-b33)
Java HotSpot(TM) Server VM (build 11.0-b15, mixed mode)
This message posted from opensolaris.org
dtrace-discuss mailing list