From: Peter Oberparleiter <oberpar@linux.vnet.ibm.com>
To: ltp-coverage@lists.sourceforge.net, ltp-list@lists.sourceforge.net
Subject: [LTP] LCOV 1.10 released
Date: Fri, 12 Oct 2012 15:01:05 +0200 [thread overview]
Message-ID: <50781491.9060402@linux.vnet.ibm.com> (raw)
Version 1.10 of the LTP GCOV extension (LCOV) has been released.
LCOV is a graphical front-end for GCC's coverage testing tool gcov. It
collects gcov data for multiple source files and creates HTML pages
containing the source code annotated with coverage information. It also
adds overview pages for easy navigation within the file structure. LCOV
supports statement, function and branch coverage measurement.
Changes in version 1.10 include:
* Support for GCC 4.7
* Improved support for complex build environments such as libtool
* New configuration setting to disable branch coverage for improved
performance
* New option to easily filter out coverage data for external files
such as standard library headers
* Multiple bug fixes and documentation improvements
Download instructions and a detailed list of changes included in this
release can be found on the LCOV web page at:
http://ltp.sourceforge.net/coverage/lcov.php
------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
reply other threads:[~2012-10-12 13:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=50781491.9060402@linux.vnet.ibm.com \
--to=oberpar@linux.vnet.ibm.com \
--cc=ltp-coverage@lists.sourceforge.net \
--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