New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 609207 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Oct 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature

Blocking:
issue 539572



Sign in to add a comment

Libfuzzer coverage layer in Code Search

Project Member Reported by aizatsky@chromium.org, May 4 2016

Issue description

ClusterFuzz  collects coverage information for fuzzers it runs. Right now we are using a standalone tool to generate individual coverage reports.

To improve usability (and visibility) of these reports we'd like to integrate the information into Chromium Code Search. A special "Libfuzzer Coverage" layer would be ideal.

The layer will provide following annotations:

- line coverage information for some lines (covered/not covered). Should be   displayed in the source.
- aggregate information per folder. (covered/uncovered blocks, covered/uncovered functions).
- function coverage information for outline view.

Coverage information ideally should also include a name of the fuzzer that generated the coverage (display it in the gutter?). 

 
Cc: och...@chromium.org mmoroz@chromium.org
Owner: aizatsky@chromium.org
Awesome. Can we make this more general and not specific to libfuzzer, ie make it work for any sancov files CF provides? 
Cc: emso@chromium.org
Status: Assigned (was: Untriaged)
Are we still planning to pursue this plan here ? If not, can you please close!.
Status: WontFix (was: Assigned)
We probably won't purse this at all.

Comment 6 by emso@chromium.org, Oct 4 2016

This is something that could be picked up later when there is a Tricium integration in code search. This will allow for display of analysis results and this could include a coverage layer. This is several quarters out so I agree that it makes sense to close this now.

Sign in to add a comment