RFR: 8372380: Make hs_err reporting more robust for unattached threads [v3]
David Holmes
dholmes at openjdk.org
Mon Nov 24 02:34:39 UTC 2025
> There were a number of places where the code called by hs_err reporting assumed/required an attached current thread. These would then cause secondary failures during hs_err reporting. Using a simple example of an unattached thread causing a SEGV I went through and eliminated all the problems I encountered. In some cases the thread dependency was obvious and easy to address directly, but in others we just skip that section at the top-level.
>
> Testing:
> - manual inspection of hs_err file, for different GCs
> - tiers 1-3 sanity
>
> Thanks
David Holmes has updated the pull request incrementally with one additional commit since the last revision:
Fix include order
-------------
Changes:
- all: https://git.openjdk.org/jdk/pull/28470/files
- new: https://git.openjdk.org/jdk/pull/28470/files/5d59c7e9..57ad332b
Webrevs:
- full: https://webrevs.openjdk.org/?repo=jdk&pr=28470&range=02
- incr: https://webrevs.openjdk.org/?repo=jdk&pr=28470&range=01-02
Stats: 2 lines in 1 file changed: 1 ins; 1 del; 0 mod
Patch: https://git.openjdk.org/jdk/pull/28470.diff
Fetch: git fetch https://git.openjdk.org/jdk.git pull/28470/head:pull/28470
PR: https://git.openjdk.org/jdk/pull/28470
More information about the hotspot-dev
mailing list