Implement a step command via agent debugging #619
Draft
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
hexploitable
changed the title
|
Frida 18 will add support for breakpoints and watchpoints. maybe better to wait for this thing |
|
the breakpoints commands should be reworked and use this pr as inspiration #630 |
trufae
force-pushed
the
master
branch
2 times, most recently
from
71557b4 to
ba873ed
Compare
|
breakpoints reworked, please resolve conflicts and rebase |
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 is an attempt to add a step feature to the existing agent based breakpoint functionality (
:db), by calculating the next instruction and setting an ephemeral breakpoint there.I tried to have the code automatically continue, but the app behaves weird. Some times it would work and sometimes hang, so unless you have ideas, we'd use this like so: