>From that debian thread: "Per logs from message #15 on bug #842796: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842796#15
SIGSEGV on __lll_unlock_elision is a signature (IME with very high confidence) of an attempt to unlock an already unlocked lock while running under hardware lock elision. Well, unlocking an already unlocked lock is a pthreads API rule violation, and it is going to crash the process on something that implements hardware lock elision." So I think we have some pretty good evidence of an application problem. I think that using Paul Clarke's suggestion may be necessary for you to figure out where the double-unlock is occurring. I'm not confident that valgrind will spot this. We're going to continue trying to reproduce on our side and disable TLE to confirm that this segv goes away. Hard to know if this is related to the original reported problem, of course, but perhaps losing TLE will allow valgrind to find that if it's a separate issue. ** Bug watch added: Debian Bug tracker #842796 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842796 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1640518 Title: MongoDB Memory corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-5/+bug/1640518/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
