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

Print more info on segfault

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None

    Description

      Currently there is very little useful information on segfault:

      Wed Dec 21 19:49:21 Invalid access at address: 0x2aaaab9c6ad0
      Wed Dec 21 19:49:21 Got signal: 11 (Segmentation fault).
      Wed Dec 21 19:49:21 Backtrace:
      0xb4c164 0xb50b2c 0x2aaaaacd5540 0x2aaaab9c6ad0 
       /mnt/home/buildbot/slave/Linux_64bit/mongo/mongod(_ZN5mongo10abruptQuitEi+0x3d4) [0xb4c164]
       /mnt/home/buildbot/slave/Linux_64bit/mongo/mongod(_ZN5mongo24abruptQuitWithAddrSignalEiP7siginfoPv+0x22c) [0xb50b2c]
       /lib64/libpthread.so.0 [0x2aaaaacd5540]
       /lib64/libc.so.6 [0x2aaaab9c6ad0]

      It seems that the address printed after "Invalid access at address" is the address of the instruction pointer in the thread that received the segfault signal. It would be nice to have the address that was actually faulted on, as well as the stack trace of the thread that triggered the segfault instead of the one that received the signal.

      Attachments

        Activity

          People

            spencer@mongodb.com Spencer Brody (Inactive)
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: