calltree coverage visualisation missing some cases #340
Comments
|
further inspection shows this is to do with the coverage build/extraction rather than fuzz introspector itself. Will leave open until I have sorted it completely though |
DavidKorczynski
added a commit
to DavidKorczynski/oss-fuzz
that referenced
this issue
Jun 29, 2022
When generating coverage reports for single targets we should not include all fuzz targets (in the $objects var), but only the object (binary file) for the given target. Ref: ossf/fuzz-introspector#340
|
This is an issue in the OSS-Fuzz coverage extraction and is fixed by google/oss-fuzz#7927 |
oliverchang
pushed a commit
to google/oss-fuzz
that referenced
this issue
Jun 30, 2022
* infra: fix per-target coverage html generation When generating coverage reports for single targets we should not include all fuzz targets (in the $objects var), but only the object (binary file) for the given target. Ref: ossf/fuzz-introspector#340 * coverage: remove potential race condition
MartinPetkov
pushed a commit
to MartinPetkov/oss-fuzz
that referenced
this issue
Aug 15, 2022
* infra: fix per-target coverage html generation When generating coverage reports for single targets we should not include all fuzz targets (in the $objects var), but only the object (binary file) for the given target. Ref: ossf/fuzz-introspector#340 * coverage: remove potential race condition
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The following screenshot is from apache-httpd. Clearly something is off
The text was updated successfully, but these errors were encountered: