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

Unknown operation taint #25

Open
JoranHonig opened this issue May 13, 2018 · 2 comments
Open

Unknown operation taint #25

JoranHonig opened this issue May 13, 2018 · 2 comments

Comments

@JoranHonig
Copy link
Collaborator

JoranHonig commented May 13, 2018

The taint analysis module prints an error message if it finds unknown operations.

JUMPDEST and ASSERT_FAIL will need to be implemented.

@muellerberndt
Copy link
Owner

These two are special bytes as opposed to actual instructions. ASSERT_FAIL is actually supposed to be an invalid instruction to cause an exception.

In a recent commit I changed the logging.error to logging.debug so the taint analysis error is shown in the debug log. Should be reasonable?

@JoranHonig
Copy link
Collaborator Author

That is reasonable. But the JUMPDEST and ASSERT_FAIL should still be implemented ( even though they don't actually change a taint record )
This could be a good first issue!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants