JDK-8294160 : misc crash dump improvements
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 20
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2022-09-22
  • Updated: 2024-10-31
  • Resolved: 2022-09-28
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 JDK 20
17.0.7-oracleFixed 20 b18Fixed
Related Reports
Relates :  
Relates :  
Description
Try to recover and output meaningful information in more situations, such as:
- when a pointer is in Method metadata memory range, but the memory is not committed
- when we call a bad address

When calling a bad address, we usually don't get a meaningful stack backtrace, but in many situations we can if we know where to find the caller information.
Comments
Thanks [~dlong] for confirming. I created JDK-8343343 to add support on more platforms. For bsd_x86 we probably can just copy the coding that was used in this change.
31-10-2024

[~mbaesken], I think it would indeed be useful on those other platforms. In hindsight, I could have pinged and gotten help from the port maintainers on the other platforms when working on the PR.
31-10-2024

Hi [~dlong] , [~dholmes] this change adjusted frame os::fetch_frame_from_context(const void* ucVoid) on linux arrch64, linux x86_64, windows x86_64 to use os::fetch_frame_from_context(uc).pc(); . Is there a reason why it was done only on those platforms and not on others (like bsd_x86, linux-ppc64 etc.) ? Is there no need for it on those platforms or was it just not done because they were seen not so important (or you could not test those) ?
30-10-2024

Submitted https://bugs.openjdk.org/browse/JDK-8307549
05-05-2023

> Low risk, touches code only used in error situation. It turns out this code is used not only for error reporting, but also for profiling. This change has broken AsyncGetCallTrace on Mac M1. I'll submit an issue shortly.
05-05-2023

Fix request [17u] I backport this for parity with 17.0.7-oracle. Low risk, touches code only used in error situation. I had to resolve. SAP nightly testing passed.
25-01-2023

A pull request was submitted for review. URL: https://git.openjdk.org/jdk17u-dev/pull/1107 Date: 2023-01-24 09:39:06 +0000
24-01-2023

Changeset: 6f8f28e7 Author: Dean Long <dlong@openjdk.org> Date: 2022-09-28 23:15:04 +0000 URL: https://git.openjdk.org/jdk/commit/6f8f28e7566701b195ecc855f3e802cd7145e9aa
28-09-2022

A pull request was submitted for review. URL: https://git.openjdk.org/jdk/pull/10387 Date: 2022-09-22 07:53:42 +0000
22-09-2022