Add libunwind patch to fix dwarf unwinding #24379
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The issue is the most significant with FPO enabled and on x86 but can in principle happen in other cases too. Upstream PR libunwind/libunwind#54
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The issue is the most significant with FPO enabled and on x86 but can in principle happen in other cases too.
Upstream PR libunwind/libunwind#54. The patch is slightly different due to the difference between libunwind master and the commit we are based on. I'm submitting/have submitted most of the patches we have upstream.
This fixes the 32bit linux failure in #24341 (We don't need frame pointer unwinding but the more complex unwind info triggered the libunwind bug...)