RFR: 8294003: Don't handle si_addr == 0 && si_code == SI_KERNEL SIGSEGVs

[Stefan Karlsson]

On Mon, 19 Sep 2022 22:27:47 GMT, Dean Long <dlong at openjdk.org> wrote:

> Is there a way to detect this on Windows too? https://bugs.openjdk.org/browse/JDK-8293832 looks like it could be because of high bits with ZGC.

I don't know.

Single-generational ZGC places most bits in "dereferenceable" memory. We only use one bit outside of that, and that bit is specifically for dealing with finalizers.

I took a look at the linked Bug. So, on Windows we get 0xffffffff reported as the failing address. Note, that even with my patch, we still get the incorrect address reported on Linux. I don't know if that's fixable. My patch only makes sure that we don't try to continue running, and then hit one of those very misleading secondary failures.

-------------

PR: https://git.openjdk.org/jdk/pull/10340