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

stacktrace: libunwind steps should be bounded

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor - P4 Minor - P4
    • 4.3.3
    • 4.3 Required
    • Internal Code
    • None
    • Fully Compatible
    • ALL
    • Hide

      see HELP-12717

       

      Show
      see HELP-12717  
    • Dev Tools 2019-12-30

    Description

      While investigating a deep stack (HELP-12717), we found that the libunwind printStackTrace implementation was doing its job and trying to give as much information as possible, but unfortunately this fills up the log statement 100k limit with just the raw instruction addrs, so all the good stuff in the stack trace is truncated. This is no good.

      Easiest fix is to just not use libunwind's cursor steps, and just always do a rawBacktrace.

      Attachments

        Activity

          People

            billy.donahue@mongodb.com Billy Donahue
            billy.donahue@mongodb.com Billy Donahue
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: