hotspot:::monitor-waited throws 'out of scratch space' error.
Looks like illegal data are passed to the probe.
Log results:
------------
dtrace: error on enabled probe ID 3 (ID 36554: hotspot958:libjvm.so:__1cSObjectSynchronizerEwait6FnGHandle_xpnGThread__v_:monitor-waited):
out of scratch space in action #1 at DIF offset 60
...
----------
See more results in attached log file.
To reproduce run:
1. java -XX:+UnlockDiagnosticVMOptions -XX:+PauseAtStartup IncrementDecrement 2 &
2. monitors_pid.d <java_pid> 2>&1 | tee monitors.log
3. grep "dtrace: error" monitors.log
to see the errors
To trace input arguments are passed to a probe 'monitor-waited' run:
1. java -XX:+UnlockDiagnosticVMOptions -XX:+PauseAtStartup 2
2. monitors_debug_pid.d <java_pid>
###@###.### 2005-06-22 13:35:41 GMT
Looks like illegal data are passed to the probe.
Log results:
------------
dtrace: error on enabled probe ID 3 (ID 36554: hotspot958:libjvm.so:__1cSObjectSynchronizerEwait6FnGHandle_xpnGThread__v_:monitor-waited):
out of scratch space in action #1 at DIF offset 60
...
----------
See more results in attached log file.
To reproduce run:
1. java -XX:+UnlockDiagnosticVMOptions -XX:+PauseAtStartup IncrementDecrement 2 &
2. monitors_pid.d <java_pid> 2>&1 | tee monitors.log
3. grep "dtrace: error" monitors.log
to see the errors
To trace input arguments are passed to a probe 'monitor-waited' run:
1. java -XX:+UnlockDiagnosticVMOptions -XX:+PauseAtStartup 2
2. monitors_debug_pid.d <java_pid>
###@###.### 2005-06-22 13:35:41 GMT