[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:
Depends
is depended on by SERVER-33445 Add signal handler to generate stack ... Closed
Related
is related to SERVER-33259 Include libunwind in src/third_party Closed
Backwards Compatibility: Fully Compatible
Sprint: Dev Tools 2019-07-15
Participants:

 Description   

Per SERVER-35935, this flag provides "increased reliability of backtraces". Should consider adding it to our default flags when supported by the toolchain.



 Comments   
Comment by Githook User [ 17/Jul/19 ]

Author:

{'name': 'Andrew Morrow', 'email': 'acm@mongodb.com', 'username': 'acmorrow'}

Message: SERVER-36178 Use -fasynchronous-unwind-tables
Branch: master
https://github.com/mongodb/mongo/commit/56f7aa61a37580a973adca93a939cf969d9130d8

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 SERVER-22359). Adding this flag might improve reliability if we generate a backtrace from a signal handler (SERVER-33445).

Generated at Thu Feb 08 04:42:17 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.