From: Peter Oberparleiter <oberpar@linux.vnet.ibm.com>
To: drberlin <drberlin@aol.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [ ltp-Feature Requests-2927507 ] lcov: branch coverage in reports
Date: Wed, 27 Jan 2010 10:36:45 +0100 [thread overview]
Message-ID: <4B60092D.70904@linux.vnet.ibm.com> (raw)
In-Reply-To: <27331504.post@talk.nabble.com>
On 27.01.2010 00:16, drberlin wrote:
> If branch coverage is implemented in lcov, I will be able test it (and
> indeed MUSTbefore using for our safety critical application). When might it
> be available?
It is implemented now in the CVS version of lcov [*].
Regards,
Peter Oberparleiter
[*] see http://ltp.sourceforge.net/coverage/lcov.php for instructions on
how to get the CVS version
------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2010-01-27 9:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 10:04 [LTP] [ ltp-Feature Requests-2927507 ] lcov: branch coverage in reports SourceForge.net
2010-01-26 23:16 ` drberlin
2010-01-27 9:36 ` Peter Oberparleiter [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-01-07 13:08 SourceForge.net
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B60092D.70904@linux.vnet.ibm.com \
--to=oberpar@linux.vnet.ibm.com \
--cc=drberlin@aol.com \
--cc=ltp-list@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox