[SERVER-40139] we should ensure implementations of all shims in output binaries Created: 14/Mar/19 Updated: 06/Dec/22 Resolved: 18/Mar/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Mira Carey | Assignee: | DO NOT USE - Backlog - Dev Tools |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Developer Tools
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
The MONGO_SHIM macros don't actually verify (at compile, link or startup) that they have implementations. We can't enforce this in the initializer graph (because the point of shim is to let us have unimplemented symbols for unittests), but we should check it for binaries intended for end user consumption. This would probably take the form of a initializer than ran after all shims, or an explicit call to some static function that checked against a global registry. |