[SERVER-29804] Undefined behaviour in the sharding catalog unit-tests Created: 22/Jun/17 Updated: 30/Oct/23 Resolved: 26/Jun/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.5.9 |
| Fix Version/s: | 3.5.10 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Kaloian Manassiev |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Sharding 2017-07-10 |
| Participants: |
| Description |
|
Almost all sharding catalog unit-tests define a static variable kReplSecondaryOkMetadata with a function initializer referencing ReadPreferenceSetting. The problem is that this initializer function can be called before ReadPreferenceSetting's static variables have been constructed, which causes the tests to crash under Windows DEBUG. |
| Comments |
| Comment by Githook User [ 26/Jun/17 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: |