Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is tracing the best option? #20

Closed
0ca opened this issue Sep 2, 2016 · 3 comments
Closed

Is tracing the best option? #20

0ca opened this issue Sep 2, 2016 · 3 comments

Comments

@0ca
Copy link
Collaborator

0ca commented Sep 2, 2016

We are using tracing to automate the process of stopping in every instruction and instrument it. But tracing is also storing in IDA a trace log with all the registers/memory modified and their original values:
image

Maybe has better performance use step_into() or step_over().

@0ca
Copy link
Collaborator Author

0ca commented Sep 2, 2016

I think we should use step into or step over and let the user to choose which one use. But also we should let the user to step manually. So we could add a menu with the option:

> Run program instrumenting instructions...
>> using step into
>> using step over

(>>) are submenus

And internally we set a flag "Automatically_continue_after_step" to true. And in the debugger callbacks for every step_into or over continue the execution transparently.

0ca added a commit that referenced this issue Sep 2, 2016
@illera88
Copy link
Owner

illera88 commented Sep 5, 2016

We should check how to use the PIN tracing because it will be way faster than any other option

0ca pushed a commit that referenced this issue Sep 6, 2016
@0ca
Copy link
Collaborator Author

0ca commented Sep 7, 2016

@illera88 illera88 assigned illera88 and unassigned illera88 Sep 8, 2016
@illera88 illera88 added this to the v0.1 milestone Sep 8, 2016
@illera88 illera88 removed this from the v0.1 milestone Sep 10, 2016
@0ca 0ca closed this as completed Sep 12, 2016
mxmssh added a commit that referenced this issue Feb 2, 2018
Added a temporal solution for VERSION_NUMBER while we are making
our pre-build script work at AppVeyor site. xref #20
illera88 pushed a commit that referenced this issue Sep 18, 2019
Added a temporal solution for VERSION_NUMBER while we are making
our pre-build script work at AppVeyor site. xref #20
illera88 pushed a commit that referenced this issue Sep 18, 2019
Added a temporal solution for VERSION_NUMBER while we are making
our pre-build script work at AppVeyor site. xref #20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants