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

Have gdb decorable pretty printers include better decoration identify

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None

      Today, printing out a decorable such as the service context or operation context in gdb will iterate its decorations and print them out.

      However, the output can be ambiguous due to only outputting the type and value. When the decoration is a complex(named) structure, it's easy to know what it represents. But we sometimes use primitives as a decoration.

      It would be an improvement if the gdb output (presumably with some accompanying server change) could include more discriminating information. Ideally this would be a variable name, e.g: getInReplicationRecovery, but that would presumably require macroing which is more invasive than I'm seeking for here. A filename (and maybe line number?) should be sufficient to at least remove the ambiguity.

            Assignee:
            schwerin@mongodb.com Andy Schwerin
            Reporter:
            daniel.gottlieb@mongodb.com Daniel Gottlieb (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: