8339772: serviceability/sa/TestJhsdbJstackUpcall.java fails on Linux ppc64le

[TheRealMDoerr]

The SA model of the UpcallStub doesn't work reliably on PPC64. We can use the Backchain which works for all Power Architecture 64-Bit ELF ABI compliant frames. (The backtrace should stop when hitting a non-compliant frame which can occur with some compiler options. Also see comment in JBS issue.)
Note that this enables walking the native frames which is possible on PPC64, but not on some other platforms due to missing backlinks.

"test/hotspot/jtreg/serviceability" tests have passed with this PR.

---

Progress

• Change must be properly reviewed (1 review required, with at least 1 Reviewer)
• Change must not contain extraneous whitespace
• Commit message must refer to an issue

Issue

• JDK-8339772: serviceability/sa/TestJhsdbJstackUpcall.java fails on Linux ppc64le (Bug - P4) ⚠️ Issue is not open.

Reviewers

• Matthias Baesken (@MBaesken - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/21092/head:pull/21092
$ git checkout pull/21092

Update a local copy of the PR:
$ git checkout pull/21092
$ git pull https://git.openjdk.org/jdk.git pull/21092/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 21092

View PR using the GUI difftool:
$ git pr show -t 21092

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/21092.diff

Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back mdoerr! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

@TheRealMDoerr This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8339772: serviceability/sa/TestJhsdbJstackUpcall.java fails on Linux ppc64le

Reviewed-by: mbaesken

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 44 new commits pushed to the master branch:

• ea8f35b: 8340183: Shenandoah: Incorrect match for clone barrier in is_gc_barrier_node
• a9b0f9c: 8340393: Open source closed choice tests Make "can write" check work on Windows #2
• 63e611c: 8335334: Stress mode to randomly execute unstable if traps
• 37ec80d: 8339161: ZGC: Remove unused remembered sets
• 384deda: 8325949: Create an internal utility method for creating VarHandle instances
• 67448b0: 8339852: Fix typos in java.compiler documentation
• bc7c0dc: 8340084: Open source AWT Frame related tests
• a07052e: 8340573: Remove unused G1ParScanThreadState::_partial_objarray_chunk_size
• 0f253d1: 8340392: Handle OopStorage in location decoder
• f31f97d: 8340171: CDS: Enhance bitmap truncation
• ... and 34 more: https://git.openjdk.org/jdk/compare/3bb8de31457a544d9c20a12f8d8d30d6d1cd9cba...master

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

[openjdk]

@TheRealMDoerr The following label will be automatically applied to this pull request:

• serviceability

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

[mlbridge]

Webrevs

• 00: Full (92213320)

[TheRealMDoerr]

GHA Pre-submit test failures look unrelated ("Unable to download artifact(s)").

[TheRealMDoerr]

Thanks for the review! I think it can be considered trivial as it basically removes new code which has never worked.

[YaSuenag]

I'm not sure whether this PR is correct - if the app has several call stacks which do not compliant the ABI, this PR would not work. See #20789 (comment) for details.

It is better to use JavaFrameAnchor like other platforms if we can.

[TheRealMDoerr]

I'm not sure whether this PR is correct - if the app has several call stacks which do not compliant the ABI, this PR would not work. See #20789 (comment) for details.

It is better to use JavaFrameAnchor like other platforms if we can.

We don't support frames which don't follow the ABI. I think stopping the backtrace immediately is an appropriate reaction. Other debuggers like GDB would do the same. Nevertheless, I couldn't spot any bug in your new code. So, I've debugged the issue and found JDK-8340657 which causes the problem.

[TheRealMDoerr]

Closing in favor of #21139.