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

i#3978: Fix decode_cti bug on particular (e)vex byte sequences #3979

Merged
merged 1 commit into from
Dec 11, 2019

Conversation

derekbruening
Copy link
Contributor

Fixes a bug in decode_cti() with a (e)vex prefix with its 2nd or 3rd
byte also looking like the first byte of a (e)vex prefix where the
instruction is considered invalid, crashing the application.

Adds testing of decode_cti() to api.ir by export decode_cti() in DEBUG
and BUILD_TESTS builds. Adds a test case that triggers the observed
bug without the fix.

Fixes #3978

Fixes a bug in decode_cti() with a (e)vex prefix with its 2nd or 3rd
byte also looking like the first byte of a (e)vex prefix where the
instruction is considered invalid, crashing the application.

Adds testing of decode_cti() to api.ir by export decode_cti() in DEBUG
and BUILD_TESTS builds.  Adds a test case that triggers the observed
bug without the fix.

Fixes #3978
@derekbruening
Copy link
Contributor Author

Wow our CI is not in a good place: all 3 failures look like flakes.

Copy link
Contributor

@Carrotman42 Carrotman42 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@derekbruening
Copy link
Contributor Author

The test failures are #3980, #3981, #3496

@derekbruening derekbruening merged commit b9d0d9e into master Dec 11, 2019
@derekbruening derekbruening deleted the i3978-decode-cti-vex branch December 11, 2019 21:54
p0wer0xff added a commit to siemens/fluffi that referenced this pull request Dec 12, 2019
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

Successfully merging this pull request may close these issues.

CRASH (7.91.18219) pc is null in decode_sizeof
2 participants