JDK-8203836 : Test serviceability/sa/ClhsdbWhere.java fails to find stacktrace for main
  • Type: Bug
  • Component: hotspot
  • Sub-Component: svc-agent
  • Affected Version: 11
  • Priority: P4
  • Status: Closed
  • Resolution: Cannot Reproduce
  • Submitted: 2018-05-25
  • Updated: 2020-03-11
  • Resolved: 2020-03-11
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.
Other
tbdResolved
Related Reports
Relates :  
JDK-8215042 - Umbrella bug for all SA failures in tier1
Description
Test serviceability/sa/ClhsdbWhere.java fails to find stack trace for main method. See full log in attachment.
Comments
While this fails very rarely in CI it does crop up in personal jobs, sometimes for different threads. Always there is a lurking error e.g. Error: java.lang.NullPointerException Error: sun.jvm.hotspot.debugger.UnmappedAddressException: 2f6176616a4c1000 Error: sun.jvm.hotspot.debugger.UnalignedAddressException: f0ce9bb1 Not clear if the test needs more diagnostics or whether Clhsdb is at fault. Seems strange to get a corrupt stacktrace.
30-05-2019
In the attached log we see a buried: Error: java.lang.NullPointerException which suggests it was encountered when trying to process the stack for the main thread. In other failures we see: Error: sun.jvm.hotspot.utilities.AssertionFailure: illegal bci
30-05-2019
Failure is very intermittent, happened only once from hundred successful runs.
25-05-2018