[SERVER-75504] Investigate DBException left uncaught even though there is a handler (gcc, opt + dbg) Created: 30/Mar/23 Updated: 02/Feb/24 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jordi Serra Torrens | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Build
|
| Participants: |
| Description |
|
On gcc builds with opt=on and dbg=on (x86, but haven't tried others) such as buildvariant "! Linux x86 Shared Library DEBUG", if I place a `uasserted` in this function which is part of a command execution, the DBException is left uncaught and crashes the server, even though there's a handler for it. The same does not reproduce on clang builds, nor on gcc builds with "opt=on dbg=off" or "opt=off dbg=on". |