On Mon, 10 Mar 2008, Brad Hards wrote:
> It appears to be working for me, although some of the output looks a bit
> strange:
> 5: 12:void TestQEmf::check()
> -: 13:{
> 9: 14: QVERIFY( true );
> 2: 15: QWinMetaFile wmf;
> 5: 16: QImage pic(1000, 800, QImage::Format_ARGB32_Premultiplied);
> 20: 17: QVERIFY( wmf.load( "1.emf" ) );
> -: 18:
> 14: 19: wmf.paint( &pic );
> 4: 20:}
>
> I'm not too worried - all I really care about is executed-or-not, but it does
> make the output look unreliable.
Why is it strange? I've seen cases where compiler optimisations make lines
that you think should be executable become non-executable, but this doesn't
seem to be one of them. Well, whether the function name line and the '{'
and '}' lines are executable depends on what the compiler does.
> I was a bit confused by the vc_annotate tool usage info - patch attached. This
> also switches it to be generated from vc_annotate.in, so the patch is a bit
> hard to read. Basically, it changes the usage to look like this:
> usage: vc_annotate [options] vcov.out (source-files...)
>
> From some initial usage, it would be most useful to be able to exclude a
> range of files and directories. For example, always exclude
> coregrind/m_trampoline.S, and provide an option so I can specify to not do
> coverage on my test harness files and some include directories.
I'm on holiday for a couple of weeks, but I'll have a look at this when I
get back. Thanks.
Nick
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Valgrind-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-developers
