monitor-contended-exit throws 'out of scratch space' error.
It seems that illegal data are passed to the probe.
Log results:
-----------------
monitor-contended-entered: thread_id=1027080, monitor_id=751312, class_name=java/io/PrintStream (len=19)
monitor-contended-enter: thread_id=1027080, monitor_id=751312, class_name=java/io/PrintStream (len=19)
trace: error on enabled probe ID 5 (ID 36861: hotspot25795:libjvm.so:__1cNObjectMonitorEexit6MpnGThread__v_:monitor-contended-exit): out of scratch space in action #1 at DIF offset 60
...
-------------
See more results in attached log files.
To reproduce run:
1. java -XX:+UnlockDiagnosticVMOptions -XX:+PauseAtStartup IncrementDecrement 1 &
2. monitors_contended_pid.d <java_pid>
To see what int64_t input arguments are passed to a probe 'monitor-contended-exit' run debug version of dtrace script:
1. java -XX:+UnlockDiagnosticVMOptions -XX:+PauseAtStartup IncrementDecrement 1 &
2. monitors_contended_debug_pid.d <java_pid>
###@###.### 2005-06-21 12:39:50 GMT
###@###.### 2005-06-22 13:31:48 GMT
It seems that illegal data are passed to the probe.
Log results:
-----------------
monitor-contended-entered: thread_id=1027080, monitor_id=751312, class_name=java/io/PrintStream (len=19)
monitor-contended-enter: thread_id=1027080, monitor_id=751312, class_name=java/io/PrintStream (len=19)
trace: error on enabled probe ID 5 (ID 36861: hotspot25795:libjvm.so:__1cNObjectMonitorEexit6MpnGThread__v_:monitor-contended-exit): out of scratch space in action #1 at DIF offset 60
...
-------------
See more results in attached log files.
To reproduce run:
1. java -XX:+UnlockDiagnosticVMOptions -XX:+PauseAtStartup IncrementDecrement 1 &
2. monitors_contended_pid.d <java_pid>
To see what int64_t input arguments are passed to a probe 'monitor-contended-exit' run debug version of dtrace script:
1. java -XX:+UnlockDiagnosticVMOptions -XX:+PauseAtStartup IncrementDecrement 1 &
2. monitors_contended_debug_pid.d <java_pid>
###@###.### 2005-06-21 12:39:50 GMT
###@###.### 2005-06-22 13:31:48 GMT