-
Notifications
You must be signed in to change notification settings - Fork 16
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
Fuzzing rocksdb doesn't work #8
Comments
Thank you for reporting the issue. I will take a look and figure out the cause as soon as possible. |
I finally had some time to look into this issue, but setting up environment to reproduce this issue is a little bit tough. I modified the Dockerfile from deepstate repository, and used the attached Dockerfile to build testleveldb repository. However, when I run TestLevelDB and DiffTestDBs, they abort immediately as they fail to initialize the database.
Would you take a look at my Dockerfile to identify what's going wrong, or provide a working Dockerfile for testleveldb repository? |
@jchoi2022 I suspect it's just that the Makefile sets the location of the databases somewhere that doesn't exist. Edit those to paths that exist and it likely works. |
Try with the new paths which are just dirs in the local directory |
Oops not the Makefile, Common.hpp. See the changes I just made. |
I think after this your dockerfile will work |
Thank you for the help, and I could successfully reproduce the issue.
I tried several versions of QEMU including 2.3.0 and 3.1.0, but the crash persists. I also tried to debug the crash for a while, but it seems tough to fix an issue in QEMU code. |
Another DeepState example: https://github.com/agroce/testleveldb
Eclipser claims to find a crashing input for the DiffTestDBs executable immediately, but it seems to be just a set of zero bytes that don't actually cause a crash. Incompatibility with something one of the DBs is doing and QEMU?
Fuzzing just leveldb works fine, so it's something RocksDB does. Not high priority, just FYI of an important fuzzing target that seems to break Eclipser.
The text was updated successfully, but these errors were encountered: