-
Bug
-
Resolution: Fixed
-
P4
-
16, 24
-
b25
-
x86_64
-
windows
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8354834 | 21.0.8-oracle | Rashmi Biswal Biswal | P4 | Resolved | Fixed | b03 |
JDK-8355152 | 21.0.8 | Goetz Lindenmaier | P4 | Resolved | Fixed | b01 |
JDK-8354833 | 17.0.16-oracle | Rashmi Biswal Biswal | P4 | Resolved | Fixed | b03 |
JDK-8355148 | 17.0.16 | Goetz Lindenmaier | P4 | Resolved | Fixed | b01 |
serviceability/sa/TestJhsdbJstackLineNumbers.java
Here's a snippet from the log file:
Output and diagnostic info for process 1083748 was saved into 'pid-1083748-output.log'
- LingeredAppWithBusyWork.busywork(int[]) @bci=2, line=64 (Interpreted frame)
c:\\ade\\mesos\\work_dir\\jib-master\\install\\jdk-16+17-754\\windows-x64-debug.jdk\\jdk-16\\fastdebug\\bin\\jhsdb.exe jstack --pid 1093388
[2020-09-21T15:42:53.761647500Z] Gathering output for process 1131356
[2020-09-21T15:42:56.819483300Z] Waiting for completion for process 1131356
[2020-09-21T15:42:56.819483300Z] Waiting for completion finished for process 1131356
Output and diagnostic info for process 1131356 was saved into 'pid-1131356-output.log'
- LingeredAppWithBusyWork.busywork(int[]) @bci=49, line=72 (Interpreted frame)
c:\\ade\\mesos\\work_dir\\jib-master\\install\\jdk-16+17-754\\windows-x64-debug.jdk\\jdk-16\\fastdebug\\bin\\jhsdb.exe jstack --pid 1093388
[2020-09-21T15:42:56.835089900Z] Gathering output for process 1137008
[2020-09-21T15:42:59.942666700Z] Waiting for completion for process 1137008
[2020-09-21T15:42:59.942666700Z] Waiting for completion finished for process 1137008
Output and diagnostic info for process 1137008 was saved into 'pid-1137008-output.log'
- LingeredAppWithBusyWork.busywork(int[]) @bci=5, line=64 (Interpreted frame)
Found Line Numbers: [64, 69, 71, 72]
LingeredApp stdout: [];
LingeredApp stderr: []
LingeredApp exitValue = 0
LingeredAppWithBusyWork finished
----------System.err:(14/1030)----------
java.lang.RuntimeException: Failed: Didn't find enough line numbers: [64, 69, 71, 72]
at TestJhsdbJstackLineNumbers.runTest(TestJhsdbJstackLineNumbers.java:165)
at TestJhsdbJstackLineNumbers.main(TestJhsdbJstackLineNumbers.java:186)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:564)
at com.sun.javatest.regtest.agent.MainWrapper$MainThread.run(MainWrapper.java:127)
at java.base/java.lang.Thread.run(Thread.java:832)
JavaTest Message: Test threw exception: java.lang.RuntimeException: Failed: Didn't find enough line numbers: [64, 69, 71, 72]
JavaTest Message: shutting down test
STATUS:Failed.`main' threw exception: java.lang.RuntimeException: Failed: Didn't find enough line numbers: [64, 69, 71, 72]
----------rerun:(49/5913)*----------
- backported by
-
JDK-8354833 serviceability/sa/TestJhsdbJstackLineNumbers.java failed with "Didn't find enough line numbers"
-
- Resolved
-
-
JDK-8354834 serviceability/sa/TestJhsdbJstackLineNumbers.java failed with "Didn't find enough line numbers"
-
- Resolved
-
-
JDK-8355148 serviceability/sa/TestJhsdbJstackLineNumbers.java failed with "Didn't find enough line numbers"
-
- Resolved
-
-
JDK-8355152 serviceability/sa/TestJhsdbJstackLineNumbers.java failed with "Didn't find enough line numbers"
-
- Resolved
-
- relates to
-
JDK-8252972 serviceability/sa/TestJhsdbJstackLineNumbers.java timed out
-
- Closed
-
- links to
-
Commit(master) openjdk/jdk17u-dev/0295161b
-
Commit(master) openjdk/jdk21u-dev/c7ce53cc
-
Commit(master) openjdk/jdk/0b1f5710
-
Review(master) openjdk/jdk17u-dev/3505
-
Review(master) openjdk/jdk21u-dev/1667
-
Review(master) openjdk/jdk/22117