[SERVER-36178] Evaluate adding -fasynchronous-unwind-tables to our build flags Created: 18/Jul/18 Updated: 29/Oct/23 Resolved: 17/Jul/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Build |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Andrew Morrow (Inactive) | Assignee: | Andrew Morrow (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | former-toolchain-epic | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Sprint: | Dev Tools 2019-07-15 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Per |
| Comments |
| Comment by Githook User [ 17/Jul/19 ] |
|
Author: {'name': 'Andrew Morrow', 'email': 'acm@mongodb.com', 'username': 'acmorrow'}Message: |
| Comment by A. Jesse Jiryu Davis [ 10/Jun/19 ] |
|
Adding this flag does not seem to affect executable size, and does not seem to affect backtraces. I tested with GCC 7.3 on Linux x86_64, using either backtrace from glibc or libunwind (during |