Functionality to begin thread tracking once a Native or Objective-C method is called #144
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
…c native or objective-c functions
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.
These changes introduce the ability to only begin stalking threads once a trigger function is called - it stops stalking once the trigger function returns.
With large Application processes on Android and iOS it is not possible to trace everything without the process crashing - this functionality introduces the ability to tightly narrow the scope of tracing so as to avoid crashing the process.
Happy to make any modifications - it's a bit hacky but it does enable iOS/Android coverage generation for targeted methods in large binaries.