Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-38819

record stack trace in handler for WT_PANIC

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Gone away
    • Icon: Major - P3 Major - P3
    • None
    • None
    • WiredTiger
    • None

    Description

      Currently, we simply call fassert() in mdb_handle_error(). This eventually calls std::abort(), and lets our signal handler record a stack trace.
      Unfortunately, because WiredTiger sets a panic flag on the WT connection, this causes all other threads that happen to call into WiredTiger to immediately return WT_PANIC. These threads will race with the panicking thread for the signal handler. Depending on who wins the race, we can sometimes record a stack trace that isn't useful.

      The proposal here is to manually record a stack trace in mdb_handle_error() before calling fassert, thus guaranteeing we get at least one stack trace that shows the actual point of panic.

      Attachments

        Activity

          People

            milkie@mongodb.com Eric Milkie
            milkie@mongodb.com Eric Milkie
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: