Use libunwind from toolchain#351
Merged
es1024 merged 1 commit intoyugabyte:masterfrom Apr 20, 2026
Merged
Conversation
es1024
force-pushed
the
libunwind-fix
branch
2 times, most recently
from
01f4b52 to
d62ceb6
Compare
SrivastavaAnubhav
approved these changes
Apr 20, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
For llvm-installer clang builds, we currently build libunwind with the llvm_libunwind dependency. This libunwind was slightly different from the toolchain libunwind we link to, leading to cases where we could not catch exceptions.
This picks up changes to our LLVM build's libunwind (that mirror the changes that thirdparty libunwind had) and changes llvm_libunwind to simply copy the libunwind library from the toolchain.