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

Back out of ASSERT in stacktrace_test.cpp

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.3.1
    • Component/s: Internal Code
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      Dev Tools 2019-09-23
    • Linked BF Score:
      0

      Description

      https://jira.mongodb.org/browse/BF-14768

      On RHEL6 buildvariants, the __libc_start_main at the bottom of a main thread's backtrace doesn't resolve to a section of memory known to the processInfo.somap in the stacktrace. Libc.so.* has a section but it has a different address.

      Maybe there is more than one section for that .so and the somap needs to be expanded.
      But in the meantime we can take out the assert. The section being missing from the somap is apparently to be expected for the stacktrace code as implemented.

      // TODO: (BF-14768) fails on RHEL6 when looking up `__libc_start_main`.              
      // ASSERT_TRUE(soEntryIter != soMap.end()) << "not in soMap: 0x{:X}"_format(btBase); 
      

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: