Both hotspot:::thread-start and hotspot:::thread-stop probes report wrong
thread_id value.
To reproduce run:
1. java -XX:+UnlockDiagnosticVMOptions -XX:+PauseAtPauseAtStartup TestThreads &
2. ./threads_pid.d <java_pid>
3. compare results produced by Java program and Dscript
###@###.### 2005-06-16 19:57:44 GMT
----
Also hotspot:::monitor-contended-enter, hotspot:::monitor-contended-entered, hotspot:::monitor-contended-exit probes report wrong thread_id value.
###@###.### 2005-06-21 12:46:55 GMT
thread_id value.
To reproduce run:
1. java -XX:+UnlockDiagnosticVMOptions -XX:+PauseAtPauseAtStartup TestThreads &
2. ./threads_pid.d <java_pid>
3. compare results produced by Java program and Dscript
###@###.### 2005-06-16 19:57:44 GMT
----
Also hotspot:::monitor-contended-enter, hotspot:::monitor-contended-entered, hotspot:::monitor-contended-exit probes report wrong thread_id value.
###@###.### 2005-06-21 12:46:55 GMT