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

Issue 759796 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Sep 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug

Blocking:
issue 759794



Sign in to add a comment

Set up a new coverage build on OSS-Fuzz

Project Member Reported by mmoroz@chromium.org, Aug 28 2017

Issue description

https://clang.llvm.org/docs/SourceBasedCodeCoverage.html

Basically, the following flags need to be added to CFLAGS / CXXFLAGS:

    -fprofile-instr-generate -fcoverage-mapping


Neither of sanitizers are needed for that build.

There are two goals here:

1) to see how many project would fail during the build 

2) to see how build sizes for different project would change

The second point may help us to debug  issue 759795 , as we need a smaller reproducer that has the same build size overhead.

 

Comment 1 by mmoroz@chromium.org, Aug 28 2017

Blocking: 759794

Comment 2 by och...@chromium.org, Aug 28 2017

Could you track this on the github issue tracker instead?

I also have a hacky patch in https://github.com/google/oss-fuzz/issues/191#issuecomment-295918258 from a while back that does this.

Comment 3 by mmoroz@chromium.org, Aug 28 2017

Sure, created the same ticket on OSS-Fuzz: https://github.com/google/oss-fuzz/issues/799

Cc: och...@chromium.org tanin@chromium.org mbarbe...@chromium.org infe...@chromium.org metzman@chromium.org
Components: -Tools>Stability>Clusterfuzz
Owner: mmoroz@chromium.org
Status: Fixed (was: Untriaged)
The build is done. And we have GitHub issue for follow-ups, closing this one.

Comment 6 by mmoroz@chromium.org, Dec 22 2017

Components: Tools>CodeCoverage

Sign in to add a comment