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

Default bitmap size of 65536 is too small for larger binaries #11

Closed
acidghost opened this issue Apr 21, 2022 · 1 comment
Closed

Default bitmap size of 65536 is too small for larger binaries #11

acidghost opened this issue Apr 21, 2022 · 1 comment

Comments

@acidghost
Copy link

The default bitmap size should be set to the same value as this, which is the default value for the bitmap size before starting the fork-server.

ATM, with the current bitmap size, I get this warning and later a crash here.

The initial bitmap will be resized by the spec-fuzzer once it gets the updated bitmap size from __afl_final_loc. This should also work outside of LTO (see here).

This can be fixed by updating the default bitmap size in the generated config.ron (or the default one for kernel / snapshot) and adding the same value in a AFL_MAP_SIZE env variable in fuzz.sh. I should be able to make a PR in the following days.

@schumilo
Copy link
Member

schumilo commented Aug 5, 2022

Fixed in commit f201fa2.

@schumilo schumilo closed this as completed Aug 5, 2022
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