Investigate bug in which gdb usage is not possible on a spawnhost if the failure came from a *san variant

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 7.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • DevProd Correctness
    • Fully Compatible
    • ALL
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      If an engineer attempts to debug a variant failure on a spawnhost, AND the variant was a *san configuration, gdb will NOT work on the spawnhost.

       

      On sanitizer variants we build with separate-debug=off which includes the debugsymbols inside of the binaries. The setup_spawnhosts scripts does some stuff which modifies the binary which makes the binary not work with gdb. If you download the binary from evergreen it does work.

       

      Max h hypothesized that adding the .gdb_index section into the executable itself (separate-debug=off) causes gdb to not recognize the executable as having produced the core dump and therefore refuses to load the debug symbols from the executable

       

      Original slack thread: https://mongodb.slack.com/archives/CR8SNBY0N/p1692653657122299

            Assignee:
            Daniel Moody
            Reporter:
            Trevor Guidry
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: