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.

Sign up for GitHub

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

Jump to bottom

Make sure we do not restart engines after disable Ponce #115

Closed

illera88 opened this issue May 20, 2020 · 1 comment

Assignees

Milestone

Owner

illera88 commented May 20, 2020 •

edited

Loading

Right now we calling triton_restart_engines() when disabling Ponce.

We should make sure the following use case works fine:

User gets at early stage the input he wants to symbolize
After symbolizing there are trash functions he wants not to trace (he may lost the track of the symbolic state and not getting accurate results) so he disables Ponce
The previous state must have been kept
We should concretize all the registers because we won't know their value anymore
Later on he enables Ponce back and the state is kept so concolic execution keeps working

Right now en disabling Ponce we triton_restart_engines() so the 3rd item in the prev list is not enforced.

The text was updated successfully, but these errors were encountered:

illera88 added this to the v0.3 milestone

illera88 self-assigned this

Owner Author

illera88 commented May 26, 2020

we should add documentation about this too

illera88 added a commit that referenced this issue


          triton engines are not disabled when ponce engine is turned off/on #115

illera88 closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment