[SERVER-12228] Invalid access/seg fault Created: 31/Dec/13  Updated: 10/Dec/14  Resolved: 31/Dec/13

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 2.5.4
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Daniel Gottlieb (Inactive) Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 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



 Comments   
Comment by Daniel Gottlieb (Inactive) [ 31/Dec/13 ]

Talked/debugged with Andrew Morrow and we determined my mac that built the mongod is using some unstable version of gcc. Downloading the official 2.5.4 build from the downloads page worked fine.

Generated at Thu Feb 08 03:27:57 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.