TLDR: weak_dylib_command is born
#40
Open
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
…nd since we only use `dylib_command` class for all types of dylib, I decided to make a new class, and assign that class as `LC_LOAD_WEAK_DYLIB`'s registry
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.
Problem
I'm writing a script to extract
LC_LOAD_WEAK_DYLIBfrom a binary, and since we only usedylib_commandclass for all types of dylib, I cannot differentiate between a regular dylib from the weak one.Solution
Make a new class
weak_dylib_command, and assign that class asLC_LOAD_WEAK_DYLIB's registry