RFR: 8302798: Refactor -XX:+UseOSErrorReporting for noreturn crash reporting
Coleen Phillimore
coleenp at openjdk.org
Fri Feb 24 14:27:04 UTC 2023
On Thu, 23 Feb 2023 08:08:33 GMT, Thomas Stuefe <stuefe at openjdk.org> wrote:
> This may be an argument for skipping hs-err reporting with UseOSErrorReporting - skipping everything, actually: the context that gets reported to Watson would be guaranteed to be the one from the real crash point. And the crash would be "fresh", as close as possible to the real crash site. I'd think that this is how UseOSErrorReporting is supposed to work, leaving crash reporting up to the OS.
We had envisioned using a Windows API that was being added in maybe Vista to transmit the hs_err_pid file to WER. I think that was why we decided to generate it. Getting a real "fresh" crash site as you say would be an improvement for us as well. I don't know how to get both.
-------------
PR: https://git.openjdk.org/jdk/pull/12651
More information about the hotspot-dev
mailing list