public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: drberlin <drberlin@aol.com>
To: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [ ltp-Feature Requests-2927507 ] lcov: branch coverage in reports
Date: Tue, 26 Jan 2010 15:16:46 -0800 (PST)	[thread overview]
Message-ID: <27331504.post@talk.nabble.com> (raw)
In-Reply-To: <E1NXttq-0004LT-2Z@h45xhf1.ch3.sourceforge.com>




SourceForge.net wrote:
> 
> Feature Requests item #2927507, was opened at 2010-01-07 14:08
> Message generated for change (Comment added) made by oberpapr
> You can respond by visiting: 
> https://sourceforge.net/tracker/?func=detail&atid=353382&aid=2927507&group_id=3382
> 
> Please note that this message will contain a full copy of the comment
> thread,
> including the initial issue submission, for this request,
> not just the latest update.
> Category: Tools
> Group: None
> Status: Open
> Resolution: None
> Priority: 5
> Private: No
> Submitted By: Stefan Kost (ensonic)
> Assigned to: Nobody/Anonymous (nobody)
> Summary: lcov: branch coverage in reports
> 
> Initial Comment:
> gcov -b can report branch coverage
> (http://gcc.gnu.org/onlinedocs/gcc/Invoking-Gcov.html#Invoking-Gcov)
> 
> There is a feature request for this featue also in
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=413834
> 
> 
> ----------------------------------------------------------------------
> 
> Comment By: Peter Oberparleiter (oberpapr)
> Date: 2010-01-21 11:04
> 
> Message:
> Assuming that branch coverage support would be implemented in lcov, could
> you test it?
> 
> ----------------------------------------------------------------------
> 
> You can respond by visiting: 
> https://sourceforge.net/tracker/?func=detail&atid=353382&aid=2927507&group_id=3382
> 
> ------------------------------------------------------------------------------
> Throughout its 18-year history, RSA Conference consistently attracts the
> world's best and brightest in the field, creating opportunities for
> Conference
> attendees to learn about information security's most important issues
> through
> interactions with peers, luminaries and emerging and established
> companies.
> http://p.sf.net/sfu/rsaconf-dev2dev
> _______________________________________________
> Ltp-list mailing list
> Ltp-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ltp-list
> 
> 
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?
-- 
View this message in context: http://old.nabble.com/--ltp-Feature-Requests-2927507---lcov%3A-branch-coverage-in-reports-tp27261761p27331504.html
Sent from the ltp-list mailing list archive at Nabble.com.


------------------------------------------------------------------------------
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

  reply	other threads:[~2010-01-26 23:16 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 [this message]
2010-01-27  9:36   ` Peter Oberparleiter
  -- 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=27331504.post@talk.nabble.com \
    --to=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