Re: static clang source code analysis (Code Review Requested)

On Mon, Nov 5, 2012 at 11:11 AM, Miklos Vajna <vmiklos@suse.cz> wrote:
> Hi Norbert,
>
> On Mon, Nov 05, 2012 at 08:22:53AM -0600, Norbert Thiebaud <nthiebaud@gmail.com> wrote:
> > I've been playing with gcov/lcov
> >
> > to get the coverage for a given module:
> >
> > 1/ build the product
> > 2/ make module.clean
> > 3/ gb_GCOV=YES make module
>
> Fine till this. I assume at this stage the unit tests of <module> is
> executed, and that will show up in the report.

yes
> I tried this with
> 'writerfilter', then executed 'cd sw; make -sr slowcheck', which
> executes the tests for writerfilter.
>
> > 4/ run lcov on workdir/
>
> Seems this dies here with:
>
> $ lcov -c -d workdir/
> Capturing coverage data from workdir/
> Found gcov version: 4.7.1
> Scanning workdir/ for .gcda files ...
> Found 113 data files in workdir/
> Processing CxxObject/writerfilter/source/ooxml/OOXMLBinaryObjectReference.gcda
> Out of memory!
>
> Can you share what lcov switches did you use that worked for you? I get
> this error ~instantly with 8G of ram, so it sounds a bit misleading.

I did not use any special flags...  but I only activated gcov for the
module 'basic'

lcov -c -d workdir/unxlngx6.pro/ -o gcov.list

on a box that has 8GB of memory too


also I running: LCOV version 1.9 I don't know it that makes a
difference, just thought I'd mention it :-)

Norbert