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

Remove LOGV2 call from printStackTrace no-LOGV2 codepath

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 5.0.12, 6.0.2, 6.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Fully Compatible
    • ALL
    • v6.0, v5.0
    • Security 2022-06-13, Security 2022-06-27
    • 45

      When printing a stack trace to somewhere other than the logging subsystem, we should maintain the invariant that we will not invoke the logging subsystem. This can cause issues for the synchronous signal handler.

            Assignee:
            gabriel.marks@mongodb.com Gabriel Marks
            Reporter:
            gabriel.marks@mongodb.com Gabriel Marks
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: