options/glibc: implement backtrace
#1385
Open
Conversation
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
Previously, pointers were only matched against symbols' base addresses, which this commit changes to correctly check against the symbols' span.
no92
force-pushed
the
backtrace
branch
4 times, most recently
from
322885e to
afdc178
Compare
This is to allow writev to be implemented in a way that makes it safe to call from signal handlers. The fallback implementation is not safe, but this is not a regression.
no92
force-pushed
the
backtrace
branch
2 times, most recently
from
a5880f7 to
8185b5a
Compare
avdgrinten
reviewed
Jul 21, 2025
Previously, it was only declared in the header but no implementation was defined in libc.so.
no92
force-pushed
the
backtrace
branch
2 times, most recently
from
b1bf169 to
b3a7afc
Compare
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.
No description provided.