RFR: 8302798: Refactor -XX:+UseOSErrorReporting for noreturn crash reporting

[Thomas Stuefe]

On Fri, 24 Feb 2023 14:23:48 GMT, Coleen Phillimore <coleenp 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.

Interesting, did you get this to work?

> 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.

We could generate the minidump before generating the hs-err file by calling MiniDumpWriteDump before error reporting. But that does not include WER, of course.

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

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