JDK-8209413 : AArch64: NPE in clhsdb jstack command
  • Type: Bug
  • Component: hotspot
  • Sub-Component: svc-agent
  • Affected Version: 8-aarch64,11,13
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: linux
  • CPU: aarch64
  • Submitted: 2018-08-13
  • Updated: 2021-09-15
  • Resolved: 2019-03-01
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 11 JDK 13 Other
11.0.14-oracleFixed 13 b11Fixed openjdk8u292Fixed
Related Reports
Relates :  
JDK-8257192 - Integrate AArch64 JIT port into 8u
Description
Below jtreg test cases may fail in AArch64

serviceability/sa/ClhsdbFindPC.java
serviceability/sa/TestClhsdbJstackLock.java
serviceability/sa/TestJhsdbJstackLock.java
serviceability/sa/TestJmapCore.java**

Initial cause of the failures is the "jstack" command in clhsdb prints incorrect or insufficient stack frame information of current running threads in aarch64 VM.
Comments
Fix Request: What: The upstream patch applies cleanly modulo a trivial match fail in the text around a change: __ blrt(r10, rscratch1); --> __ blr(r10); n.b. this match failure was caused by the patch which replaced the AARCH64-simulator-specific blrt calls with a simple blr. Why: This fixes some potential crashes in SA tools Testing: Tier1 tests complete as before. SA tests listed above no longer fail with NPE. 3 of the tests now pass Test ClhsdbFindPC is still failing because of the follow-on problem reported in JDK-8229118
22-08-2019
URL: http://hg.openjdk.java.net/jdk/jdk/rev/2bd3e05d4c6f User: njian Date: 2019-03-01 04:08:12 +0000
01-03-2019
Review thread: https://mail.openjdk.java.net/pipermail/serviceability-dev/2019-February/026850.html
01-03-2019
Test failures are caused by this NullPointerException while generating a stack trace: java.lang.NullPointerException at jdk.hotspot.agent/sun.jvm.hotspot.tools.StackTrace.run(StackTrace.java:83) at jdk.hotspot.agent/sun.jvm.hotspot.CommandProcessor$24.doit(CommandProcessor.java:1066) at jdk.hotspot.agent/sun.jvm.hotspot.CommandProcessor.executeCommand(CommandProcessor.java:1974) at jdk.hotspot.agent/sun.jvm.hotspot.CommandProcessor.executeCommand(CommandProcessor.java:1944) at jdk.hotspot.agent/sun.jvm.hotspot.CommandProcessor.run(CommandProcessor.java:1824) at jdk.hotspot.agent/sun.jvm.hotspot.CLHSDB.run(CLHSDB.java:99) at jdk.hotspot.agent/sun.jvm.hotspot.CLHSDB.main(CLHSDB.java:40) at jdk.hotspot.agent/sun.jvm.hotspot.SALauncher.runCLHSDB(SALauncher.java:191) at jdk.hotspot.agent/sun.jvm.hotspot.SALauncher.main(SALauncher.java:439)
28-01-2019
Recently we verified these tests again. Now they are passed.
26-12-2018