JDK-8228649 : [PPC64] SA reads wrong slots from interpreter frames
  • Type: Bug
  • Component: hotspot
  • Sub-Component: svc
  • Affected Version: 11,13,14
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • CPU: ppc
  • Submitted: 2019-07-26
  • Updated: 2022-11-15
  • Resolved: 2019-08-02
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 JDK 14
11.0.5Fixed 13.0.2Fixed 14 b09Fixed
Related Reports
Duplicate :  
JDK-8211767 - jtreg: Some SA tests are failing on PPC64
Relates :  
JDK-8209790 - SA tools not providing option to connect to debug server
Relates :  
JDK-8297082 - Remove sun/tools/jhsdb/BasicLauncherTest.java from problem list
Sub Tasks
JDK-8297082 :  
Remove sun/tools/jhsdb/BasicLauncherTest.java from problem list - New
Description
The jtreg test "serviceability/sa/sadebugd/DebugdConnectTest.java" fails with "AssertionFailure: result must >= than stack pointer".
The Java code doesn't read the right slots for the interpreter frame's monitors.

Steps to fix it:
- Make frame layout consistent between dbg and product build. Can be done by removing additional "reserved" slot which only exists in dbg builds. We can live without it.
- Implement offsets accordingly in PPC64Frame.java.
- As additonal improvement, initialize all relevant frame slots in generate_fixed_frame. Tools may access them before the interpreter writes useful content to them.
Comments
Fix request (13u) We see this error in 13u as well, fix has already been backported to 11.0.5. It's ppc specifc. Patch applies cleanly, will run through SAP's regression testing.
08-10-2019
Fix Request I saw jdk/jfr/cmd/TestPrintXML.java crashing when it tries to access the stack. This change makes sure the stack is properly initialized. So I'd like to downport it to assure proper operation of SA and jfr. Risk: some. Changes stack handling. But the change is thoroughly tested, as it has been running in all our testing since it was pushed in jdk/jdk. The part of the change that adapts the ProblemList does not appliy clean. Thus I needed a review for the trivial adaptions: http://mail.openjdk.java.net/pipermail/jdk-updates-dev/2019-August/001652.html
14-08-2019
URL: https://hg.openjdk.java.net/jdk/jdk/rev/91bc70505019 User: mdoerr Date: 2019-08-02 09:32:47 +0000
02-08-2019
Fixes following serviceability/sa tests on PPC64: ClhsdbCDSJstackPrintAll.java ClhsdbFindPC.java ClhsdbInspect.java ClhsdbJdis.java ClhsdbJstack.java ClhsdbPrintAs.java ClhsdbSource.java ClhsdbWhere.java JhsdbThreadInfoTest.java TestClhsdbJstackLock.java TestJhsdbJstackLock.java
30-07-2019