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

Why the report-data only contains the code covrage data? #1972

Open
xubenji opened this issue Apr 20, 2024 · 3 comments
Open

Why the report-data only contains the code covrage data? #1972

xubenji opened this issue Apr 20, 2024 · 3 comments

Comments

@xubenji
Copy link

xubenji commented Apr 20, 2024

I want to generate data about bugs. Do you know how to adjust it?

@xubenji
Copy link
Author

xubenji commented Apr 20, 2024

Where I can find the crash numbers?

@Ice1187
Copy link

Ice1187 commented May 17, 2024

When running experiments, choose the benchmarks that have type: bug in their benchmark.yaml, then the report will contain bug-coverage-related information. An example report can be found here. Currently, the benchmarks with bug type are:

bloaty_fuzz_target_52948c/benchmark.yaml:type: bug
harfbuzz_hb-shape-fuzzer_17863b/benchmark.yaml:type: bug
php_php-fuzz-parser_0dbedb/benchmark.yaml:type: bug
mbedtls_fuzz_dtlsclient_7c6b0e/benchmark.yaml:type: bug
libxml2_xml_e85b9b/benchmark.yaml:type: bug

You can find the crashes in the /tmp/experiment-data/experiment-folders/[benchmark]-[fuzzer]/trail-[N]/crashes directory.

@kd610
Copy link

kd610 commented Sep 1, 2024

Hi there and @Ice1187 . Is there any possible way of making a bug targeting benchmark dataset manually?

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

3 participants