To aid analyzing errors during error reporting, it would be useful to see callstacks for secondary errors.
But printing callstacks during error reporting is dangerous (may cause infinite recursion and therefore break the hs-err file also too verbose, so this feature should be off by default and probably limited to debug builds.
But printing callstacks during error reporting is dangerous (may cause infinite recursion and therefore break the hs-err file also too verbose, so this feature should be off by default and probably limited to debug builds.
- relates to
-
JDK-8296469 Instrument VMError::report with reentrant iteration step for register and stack printing
-
- Resolved
-
