Frida script improvements #91
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
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.
This expands the manual single function listening to support pattern matching and the full function context rather than just classname for logging. Eventually it would be nice to use pattern matching/globbing similar to frida-trace (ApiResolver / enumerateMatches matching) but the included regex bas should be a fine launching point.
If this PR is of interest I will clean it up a bit more, maybe add support for the -P command line option to pass regexes directly (or maybe just a .json config file) rather than hardcoding into the JS.
Also improves the docs a bit to make it easier for users to get started.
Not sure if the way I expose/use
getFunctionName4Idais best but it seemed like the best solution