-
Notifications
You must be signed in to change notification settings - Fork 10.6k
Use __ehdr_start on ELF instead of calling dladdr().
#85012
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
grynspan
wants to merge
5
commits into
main
Choose a base branch
from
jgrynspan/use__ehdr_start
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+38
−84
Open
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
d164e95
Use `__ehdr_start` on ELF instead of calling `dladdr()`.
grynspan 9054bcc
Fall back to __dso_handle if __ehdr_start is missing at runtime
grynspan 9b8b924
Can't use SymbolInfo here, use dladdr() directly
grynspan 038526e
Fix typo
grynspan 69bd6cd
Restore swift_getMetadataSectionBaseAddress() for testing purposes
grynspan File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are you sure about this? Can you point to the ELF specification where this would be the case? I believe that
__ehdr_startis the edge case - it is a GNU extension.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Both GNU binutils and LLVM's linker define it, and thus AFAICT Linux and FreeBSD define it. Android defines it too (see e.g. https://android.googlesource.com/platform/bionic/+/main/linker/linker_main.cpp). OpenBSD is an open question for me (no pun intended) which is why I pinged @3405691582 for assistance.
There appears to be chatter in the Google results about it either: not being defined when a linker script is used; or not being defined if the ELF header isn't in the same loadable section as the program headers. I'm having a fair bit of trouble actually getting concrete info here, which is why I've added this fallback path in the first place.