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

Unhandled hang analyzer exception escapes loop to get threads from each process

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.4.9, 3.5.12
    • Component/s: Testing Infrastructure
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v3.4
    • Sprint:
      TIG 2017-06-19, TIG 2017-08-21
    • Linked BF Score:
      0

      Description

      Happened on Solaris as part of an Evergreen task timeout:

      [2017/04/14 18:04:33.677] terminate called after throwing an instance of 'gdb_exception_RETURN_MASK_ERROR'
      [2017/04/14 18:04:34.794]   200  Thread 166
      [2017/04/14 18:04:35.043] Bad exit code -6
      [2017/04/14 18:04:35.043] Traceback (most recent call last):
      [2017/04/14 18:04:35.043]   File "buildscripts/hang_analyzer.py", line 732, in <module>
      [2017/04/14 18:04:35.044]     main()
      [2017/04/14 18:04:35.044]   File "buildscripts/hang_analyzer.py", line 700, in main
      [2017/04/14 18:04:35.044]     options.dump_core and check_dump_quota(max_dump_size_bytes, dbg.get_dump_ext()))
      [2017/04/14 18:04:35.044]   File "buildscripts/hang_analyzer.py", line 381, in dump_info
      [2017/04/14 18:04:35.044]     logger)
      [2017/04/14 18:04:35.044]   File "buildscripts/hang_analyzer.py", line 56, in call
      [2017/04/14 18:04:35.044]     raise Exception()
      [2017/04/14 18:04:35.044] Exception
      [2017/04/14 18:04:35.084] Command failed: exit status 1
      

        Attachments

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: