[SERVER-44323] Investigate ASAN Static initialization order fiasco check Created: 30/Oct/19 Updated: 27/Nov/19 Resolved: 27/Nov/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Mark Benvenuto | Assignee: | Andrew Morrow (Inactive) |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Dev Platform 2019-12-02 | ||||||||
| Participants: | |||||||||
| Description |
|
This ticket represents to work to determine to investigate if this is an issue that ASAN should have caught. |
| Comments |
| Comment by Andrew Morrow (Inactive) [ 27/Nov/19 ] | |
|
I built the parent commit of the fixing commit in Since there is not enough information recorded in the associated tickets to know what objects were involved in the observed initialization order fiasco, I'm closing this ticket as incomplete: without knowing what objects were involved we can't make a determination if one of them was a windows-only object, which was my hypothesis for why ASAN couldn't find it. | |
| Comment by Mark Benvenuto [ 27/Nov/19 ] | |
|
As I stated in the description of the bug, it is detected on Windows un-optimized builds. Windows, un-optimized build
To repro, just start mongod.exe. | |
| Comment by Andrew Morrow (Inactive) [ 22/Nov/19 ] | |
|
mark.benvenuto - Do you have any information on what object exhibited the init order fiasco w.r.t. the file scoped static in version.cpp? The original ticket | |
| Comment by Andrew Morrow (Inactive) [ 22/Nov/19 ] | |
|
mark.benvenuto - Do you have any information on what object exhibited the init order fiasco w.r.t. the file scoped static in version.cpp? The original ticket |