JDK-8261929 : ClhsdbFindPC fails with java.lang.RuntimeException: 'In java stack' missing from stdout/stderr
  • Type: Bug
  • Component: hotspot
  • Sub-Component: svc-agent
  • Affected Version: 17
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2021-02-17
  • Updated: 2021-04-06
  • Resolved: 2021-02-20
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 17
17 b11Fixed
Related Reports
Relates :  
JDK-8243455 - Many SA tests can fail due to trying to get the stack trace of an active method
Relates :  
JDK-8264775 - ClhsdbFindPC still fails with java.lang.RuntimeException: 'In java stack' missing from stdout/stderr
Relates :  
JDK-8261702 - ClhsdbFindPC can fail due to PointerFinder incorrectly thinking an address is in a .so
Description
 ----------System.err:(32/1608)----------
 stdout: [ + findpc 0x0000000000000000
Address 0x0: In unknown location
];
 stderr: [ + findpc 0x0000000000000000
Address 0x0: In unknown location
]
 exitValue = -1

java.lang.RuntimeException: Test ERROR java.lang.RuntimeException: 'In java stack' missing from stdout/stderr

at ClhsdbFindPC.testFindPC(ClhsdbFindPC.java:242)
at ClhsdbFindPC.main(ClhsdbFindPC.java:264)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:78)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at com.sun.javatest.regtest.agent.MainWrapper$MainThread.run(MainWrapper.java:127)
at java.base/java.lang.Thread.run(Thread.java:831)
Caused by: java.lang.RuntimeException: 'In java stack' missing from stdout/stderr
Comments
Changeset: 0825bc55 Author: Chris Plummer <cjplummer@openjdk.org> Date: 2021-02-20 20:48:00 +0000 URL: https://git.openjdk.java.net/jdk/commit/0825bc55
20-02-2021
I've been unable to reproduce this issue, but since it turned up twice in two days, and JDK-8243455 won't address this issue for a while, I think a quick fix that checks for the 0x0 address is appropriate.
18-02-2021