All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Oberparleiter <oberpar@linux.vnet.ibm.com>
To: subrata@linux.vnet.ibm.com
Cc: ltp-list <ltp-list@lists.sf.net>,
	ltp-coverage <ltp-coverage@lists.sourceforge.net>
Subject: Re: [LTP] [Ltp-coverage] Finding True Application Code Coverage in case of heteregenous	Executable Environment
Date: Mon, 31 Jan 2011 13:21:34 +0100	[thread overview]
Message-ID: <4D46A94E.8000509@linux.vnet.ibm.com> (raw)
In-Reply-To: <1296415709.29830.8.camel@subratamodak.linux.ibm.com>

Hi Subrata,

On 30.01.2011 20:28, Subrata Modak wrote:
> Is there a way to find true application code coverage for a
> heterogeneous Executable Environment, where the application can consist
> of:

Short answer: no

>       1. C Programs(only for which .gcno and .gcda files can be
>          generated)

Simply use lcov with gcc.

>       2. Shell Scripts,

See http://code.google.com/p/shcov/

>       3. Perl Scripts,

See http://search.cpan.org/~pjcj/Devel-Cover-0.73/lib/Devel/Cover.pm

I've started work on converting code coverage data from that tool into 
lcov format but haven't finished that yet.

>       4. Python Scripts,

I don't have experience with python.

>       5. etc ?

Code coverage measurements all rely on target language specific 
mechanisms. There is no universal mechanism to collect code coverage 
from any language.

> Is there any by which i can also count the no. of lines/ branches/
> Functions executed by the Scripts ??

See the references above.

> Another question. when i tried to execute the following, it took into
> consideration only the .gcda of the C executables invoked by the
> program:
>       1. lcov --directory /root/LTP-GIT/ltp/ --zerocounters
>       2. (cd /opt/ltp/; ./runltp -f math)
>       3. lcov --directory /root/LTP-GIT/ltp/ --capture --output-file
>          app.info
>       4. genhtml app.info
>
> Instead i wanted it consider all C files for which .gcno are present
> and .gcda are not present(as i did not execute the corresponding
> binaries), so to truly find the exact % of C files covered and % left
> out from the whole trickled down /root/LTP-GIT/ltp/ directory.

That is what the --initial option of lcov is for. See the man page of 
lcov for more information.


Regards,
   Peter


------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires 
February 28th, so secure your free ArcSight Logger TODAY! 
http://p.sf.net/sfu/arcsight-sfd2d
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

      reply	other threads:[~2011-01-31 12:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-30 19:28 [LTP] Finding True Application Code Coverage in case of heteregenous Executable Environment Subrata Modak
2011-01-31 12:21 ` Peter Oberparleiter [this message]

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=4D46A94E.8000509@linux.vnet.ibm.com \
    --to=oberpar@linux.vnet.ibm.com \
    --cc=ltp-coverage@lists.sourceforge.net \
    --cc=ltp-list@lists.sf.net \
    --cc=subrata@linux.vnet.ibm.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.