GDB is unable to read debug symbols when run by core analyzer

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Critical - P2
    • None
    • Affects Version/s: None
    • Component/s: Testing Infrastructure
    • None
    • DevProd Correctness
    • ALL
    • Correctness 2025-07-14
    • None
    • 2
    • Day
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When the core analyzer runs GDB, we aren't seeing GDB attempt to read from the mongod.debug separate debug symbol file.

      [2025/06/25 20:45:01.628] Reading symbols from /data/mci/046946f73b45ef04d01b3371c9817cd6/src/core-analyzer/install/dist-test/bin/mongod...
      [2025/06/25 20:45:01.628] (No debugging symbols found in /data/mci/046946f73b45ef04d01b3371c9817cd6/src/core-analyzer/install/dist-test/bin/mongod)
      [2025/06/25 20:45:01.628] Detected binary built with GCC: 14.2.0
      

      I suspect the issue is related to the recalc_debuglink() function either not running at all or not running as desired. Its purpose is to set the .gnu_debuglink section in the executable file to point at the .debug file which is one method for GDB to discover the location.

            Assignee:
            Trevor Guidry
            Reporter:
            Max Hirschhorn
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: