RFR: 8296469: Instrument VMError::report with reentrant iteration step for register and stack printing
Thomas Stuefe
stuefe at openjdk.org
Thu Nov 10 05:46:20 UTC 2022
On Wed, 9 Nov 2022 20:33:35 GMT, Dean Long <dlong at openjdk.org> wrote:
> We could also consider wrapping error reporting steps with an exception handler, rather than spending time tracking down every possible way they could crash. So instead of entering error reporting recursively, we back-track, skip the current step or sub-step, and continue. We lose information about why that step crashed, however. The "exception handler" could be implemented with something like sigsetjmp/siglongjmp.
I think the "never unwind stack" is a deliberate decision. If you unwind the stack, e.g. using longjmp, you risk errors in the follow up STEPs. E.g. by tearing ResourceMark chains.
-------------
PR: https://git.openjdk.org/jdk/pull/11017
More information about the hotspot-dev
mailing list