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

Invalid access/seg fault

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Major - P3 Major - P3
    • None
    • 2.5.4
    • None
    • None
    • ALL

    Description

      I've been able to reproduce this issue in an unfortunately complicated local development environment. I have `-vv` logs, level 2 profiling and data files which I'll upload and make available privately.

      Invalid access at address: 0 from thread: conn135
      Got signal: 11 (Segmentation fault: 11).
      Backtrace:
      0x1007bb4d6 0x1021f44d0 
       0   mongod                              0x00000001007bb4d6 _ZN5mongo15printStackTraceERSo + 38
       1   libstdc++.6.dylib                   0x00000001021f44d0 _ZTVSt15basic_stringbufIcSt11char_traitsIcESaIcEE + 16

      Attachments

        Activity

          People

            Unassigned Unassigned
            daniel.gottlieb@mongodb.com Daniel Gottlieb (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: