Try extending the ELF code segment in vibes-patch
#242
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
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.
As an alternative to the user-provided external patch spaces, it turns out that we can do a minimally-invasive edit to the program header entry of the main code segment, i.e. simply extending its size. The inspiration came from this Binary Ninja plugin I found: https://github.com/jeffli678/bnhook/blob/master/hookmanager.py#L76
I've observed that there is a decent amount of space between the end of the code segment and the next segment that gets loaded into memory (usually the data segment). The biggest surprise to me is that this technique actually works for how simple it is.