Don't call LOGV2 in the boost logging exception handler

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 6.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • Security 2022-06-27
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Since boost logging exceptions may occur during doLogImpl, this has the potential to re-enter doLogImpl, which is decidedly not reentry-safe. A couple of possible solutions:

      • Add the log entry to a queue, which is popped by some forever-running handler thread.
      • Don't log, and instead output the log message to stderr.

              Assignee:
              Sergey Galtsev (Inactive)
              Reporter:
              Gabriel Marks
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: