Avoid secondary crashes when reporting registers contents of a crash

XMLWordPrintable

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: P4
    • tbd
    • Affects Version/s: 17
    • Component/s: hotspot

      I've seen many crash report where our crash handlers crashers again while reporting the contents of registers from the original crash (ex https://bugs.openjdk.java.net/browse/JDK-8247846)

      It's unhelpful and not very professional. Is there a way we can validate the registers before attempting to print out their values and risk crashing?

            Assignee:
            Unassigned
            Reporter:
            Gerard Ziemski (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: