[SERVER-4855] Shell segfaults when doing db.foo.find() from quickstart Created: 02/Feb/12 Updated: 30/Mar/12 Resolved: 03/Feb/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Shell, Stability |
| Affects Version/s: | 2.0.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Hans-Rolf Harting | Assignee: | Michael A. Fiedler |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | crash | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Fedora 16 3.2.2-1.fc16.x86_64 #1 SMP Thu Jan 26 03:21:58 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux |
||
| Operating System: | Linux |
| Participants: |
| Description |
|
I've just tried the Quickstart from http://www.mongodb.org/display/DOCS/Quickstart+Unix and the shell crashes with a segfault: [haro@foundation node]$ mongo ) Thu Feb 2 22:55:57 0x46a9ef 0x462744 0x7f2312f14300 0x4c7590 0x7f23143ab23f 0x7f23143ae55b 0x7f23143af12c 0x7f2314396360 0x7f23143a5ae5 0x7f23143a7772 0x7f231431fcb5 0x7f231431fdb2 0x7f231431fe52 0x4d0549 0x467641 0x45ebae 0x7f2312eff69d 0x461699 The server doesn't notice this: [root@foundation node-v0.6.9]# mongod |
| Comments |
| Comment by Michael A. Fiedler [ 04/Feb/12 ] |
|
I have also tested their build, and this particular issue seems to have subsided. |
| Comment by Pau Aliagas [ 04/Feb/12 ] |
|
Fixed in latest update mongodb-2.0.2-8.fc16.x86_64 (currently in updates-testing). |
| Comment by Michael A. Fiedler [ 03/Feb/12 ] |
|
Fedora bug opened here: https://bugzilla.redhat.com/show_bug.cgi?id=787246 |
| Comment by Michael A. Fiedler [ 03/Feb/12 ] |
|
Successfully reproduced the problem using Fedora's distribution on 3.2.2-1.fc16.x86_64 #1 SMP. I have installed the 10gen-built RPM, as recommended here: http://www.mongodb.org/display/DOCS/CentOS+and+Fedora+Packages and confirmed that this works as expected. I am closing this case here, as it is not an issue on our end, and will open one with Fedora. |
| Comment by Tad Marshall [ 03/Feb/12 ] |
|
Our builds are statically linked with SpiderMonkey 1.7, the Fedora-built version is using dynamic linking to libmozjs185.so, so SpiderMonkey version 1.85. We could try a static build with 1.85 to narrow it down. The SpiderMonkey 1.85 Release Notes page ( https://developer.mozilla.org/en/SpiderMonkey/1.8.5 ) has some info: "SpiderMonkey 1.8.5 is not binary-compatible with previous releases, nor is it source-code compatible. Many JSAPI types, functions, and callback signatures have changed, though most of them still have the same names and do the same things. Applications will need significant changes ..." |
| Comment by Michael A. Fiedler [ 03/Feb/12 ] |
|
Update: I can reproduce this failure, further investigation forthcoming. |
| Comment by Eliot Horowitz (Inactive) [ 03/Feb/12 ] |
|
Yes - please report there - and can link back to here. |
| Comment by Hans-Rolf Harting [ 03/Feb/12 ] |
|
Right, same here. The package comes from the stable fedora 16 release. |
| Comment by Pau Aliagas [ 03/Feb/12 ] |
|
Same probem here. Installation comes from latest Fedora rpm mongodb-2.0.2-5.fc16.x86_64. |
| Comment by Eliot Horowitz (Inactive) [ 03/Feb/12 ] |
|
Where did this binary come from? |