[SERVER-57510] Re-investigate applicability of __GLIBCXX_DEBUG Created: 07/Jun/21 Updated: 03/Feb/23 Resolved: 13/Sep/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Andrew Morrow (Inactive) | Assignee: | [DO NOT ASSIGN] Backlog - Server Development Platform Team (SDP) (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | post-v4-toolchain | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Server Development Platform
|
||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 130 | ||||||||||||
| Description |
|
In the past, we found that GCC had bugs that prevented us from using __GLIBCXX_DEBUG, so we weren't able to turn it on by default for --dbg=on builds, or even stand up a dedicated builder. We should investigate whether those bugs are resolved when we have a v4 toolchain, as it would help us to catch things like iterator invalidation bugs in our container usage. |