[SERVER-15642] Passing an integer as a collection name to validate causes a segfault Created: 14/Oct/14 Updated: 11/Jul/16 Resolved: 20/Oct/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Stability |
| Affects Version/s: | 2.7.8 |
| Fix Version/s: | 2.7.8 |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | David Hows | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Steps To Reproduce: | > db.runCommand("validate") ) |
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
If you run the "validate" command via the string runCommand string syntax you will segfault the server, as this runs on an invalid collection This looks like a regression in the 2.7.8 branch, as this correctly returns an error in 2.7.7 |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 20/Oct/14 ] |
|
fixed in |