Skip to content

Conversation

frankomosh
Copy link

added 226 new corpus files (924K total) for the script_interpreter target

I generated these files rom an empty corpus using different fuzzing scenarios:

  1. FUZZ=script_interpreter build_fuzz/bin/fuzz -max_total_time=600 fresh_corpus/script_interpreter/

  2. FUZZ=script_interpreter build_fuzz/bin/fuzz -max_total_time=1800 fresh_corpus/script_interpreter/

  3. FUZZ=script_interpreter build_fuzz/bin/fuzz -use_value_profile=1 -max_total_time=900 fresh_corpus/script_interpreter/

  4. FUZZ=script_interpreter build_fuzz/bin/fuzz -set_cover_merge=1 -shuffle=0 -prefer_small=1 optimized_corpus/script_interpreter/ fresh_corpus/script_interpreter/

The coverage impact is as follows;

  • 1079 new coverage edges
  • 23757 new features
  • 226 unique test cases

@maflcko
Copy link
Contributor

maflcko commented Apr 15, 2025

Please squash your commits according to https://github.com/bitcoin/bitcoin/blob/master/CONTRIBUTING.md#squashing-commits

@maflcko
Copy link
Contributor

maflcko commented Apr 15, 2025

Also, I am not seeing any difference in coverage:

script_interpreter                       #637	DONE   cov: 1910 ft: 12730 corp: 552/45Mb lim: 1042390 exec/s: 1 rss: 546Mb

@frankomosh
Copy link
Author

Also, I am not seeing any difference in coverage:

script_interpreter                       #637	DONE   cov: 1910 ft: 12730 corp: 552/45Mb lim: 1042390 exec/s: 1 rss: 546Mb

Thanks @maflcko . I just realized that I started from an empty corpus and couldn't figure out that there is an overlap. I'll just close this now.

@frankomosh frankomosh closed this Apr 15, 2025
@frankomosh frankomosh deleted the add-script-interpreter-corpus branch April 20, 2025 19:15
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

Successfully merging this pull request may close these issues.

2 participants