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

Better duplicate overlap group detection #8

Open
kristopher-pellizzi opened this issue Mar 10, 2022 · 0 comments
Open

Better duplicate overlap group detection #8

kristopher-pellizzi opened this issue Mar 10, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@kristopher-pellizzi
Copy link
Owner

Currently, to check if a certain overlap group is already stored, we compare memory accesses by comparing the content of their corresponding shadow memory.
In some cases, (e.g. if access size is 4 B), this compares also some unrelated bytes status (i.e. the status of the 4 bytes stored in the same shadow byte, but not related to the memory access).
So, if they are different, the algorithm does not match them, thus creating a new overlap group, even if the hash and the memory accesses are actually the same.

To solve this, we could compute the uninitialized interval and compare that.
Of course, this may consume much more time for each detected uninitialized read.

Checj if the solution is worth the additional overhead.

@kristopher-pellizzi kristopher-pellizzi added the enhancement New feature or request label Mar 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant