-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
qcms doesn't have much as much coverage as it should. #5380
Comments
@catenacyber - does your recent fix fix this ? |
@jrmuizel thanks for this report. As rustc optimizations are disabled to build the fuzz targets for coverage cf rust-lang/rust#82144 Could you try locally with the corpus downloaded to path/to/corpus/ and using #5385 ?
You can also check the log from the fuzz target running on the coverage in the file |
Yeah, it's believable that debug_asserts! would be causing this. qcms triggers debug_asserts! in weird scenarios so they're not usable for fuzzing. |
Let me know if it improves in the next few days |
I think qcms coverage runs may also fail because of overflow checks that trigger that wouldn't trigger in release builds. |
Buffer overflow or integer overflow ? |
Interger overlow. But you're right, those checks are disabled by |
The latest coverage report looks a lot better: |
If you look at the new Rust coverage reports for qcms, the coverage is really limited with the initial lines of the fuzz harness only being executed 4 times:
https://storage.googleapis.com/oss-fuzz-coverage/qcms/reports/20210312/linux/src/mozilla-central/gfx/qcms/fuzz/fuzz_targets/fuzz_target_qcms.rs.html
Given the size of the corpus this doesn't seem correct. Further, there are open crashes for areas of the code not covered by the coverage report.
The text was updated successfully, but these errors were encountered: