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

For "IN" fuzzing the 2nd operand is meaningless #4

Open
klaus-vb opened this issue Apr 22, 2024 · 1 comment
Open

For "IN" fuzzing the 2nd operand is meaningless #4

klaus-vb opened this issue Apr 22, 2024 · 1 comment

Comments

@klaus-vb
Copy link

The "in ax,dx" instruction has just one input operand. Pre-populating the value of ax is meaningless, because it will be overwritten by the instruction. Should speed up fuzzing quite a lot.

@nstarke
Copy link
Owner

nstarke commented Jun 9, 2024

I will look into this, but one of my questions would be is if the machine code differs between in ax, dx and in ax. If there is no difference, then I think the solution you have proposed is optimal, however, if they are different they probably both still need to be fuzzed, even if we don't set dx to a specific random value before hand. What do you think @klaus-vb ?

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