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

Log each ScopedDebugInfo on a separate log line

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Server Programmability
    • SP Prioritized List

      Right now if formatting a ScopedDebugInfo hits a segfault, we won't output any information about the prior ScopedDebugInfos on the stack. (Note that SERVER-98667 takes care of the case where we hit a tassert/uassert.)

      One approach would be to implement some sort of ScopedDebugInfoStack iterator that would replace the current callers of ScopedDebugInfoStack::getAll. However, the current approach that prevents re-entrancy would have to be modified, and the callers of ScopedDebugInfoStack::getAll would likely have to deal with more complexity.

      cc ryan.berryhill@mongodb.com

            Assignee:
            Unassigned Unassigned
            Reporter:
            militsa.sotirova@mongodb.com Militsa Sotirova
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: