-
Notifications
You must be signed in to change notification settings - Fork 70
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
Comments
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:
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. |
We should check how to use the PIN tracing because it will be way faster than any other option |
Semtrax was using PIN: In the future we should try it. |
Added a temporal solution for VERSION_NUMBER while we are making our pre-build script work at AppVeyor site. xref #20
Added a temporal solution for VERSION_NUMBER while we are making our pre-build script work at AppVeyor site. xref #20
Added a temporal solution for VERSION_NUMBER while we are making our pre-build script work at AppVeyor site. xref #20
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](https://cloud.githubusercontent.com/assets/5008707/18188238/723ba1c0-7065-11e6-80d1-e1dcff360be0.png)
Maybe has better performance use step_into() or step_over().
The text was updated successfully, but these errors were encountered: