public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
* [Bug translator/4529] New: tapset coverage option
@ 2007-05-21 15:46 fche at redhat dot com
  2007-05-24 20:21 ` [Bug translator/4529] " wcohen at redhat dot com
  0 siblings, 1 reply; 2+ messages in thread
From: fche at redhat dot com @ 2007-05-21 15:46 UTC (permalink / raw)
  To: systemtap

The translator should be able to compute test coverage data for tapsets.
There are still some that don't have test cases, never mind documentation,
and a machine nagging about that would be healthy.

-- 
           Summary: tapset coverage option
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: translator
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: fche at redhat dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=4529

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

^ permalink raw reply	[flat|nested] 2+ messages in thread

* [Bug translator/4529] tapset coverage option
  2007-05-21 15:46 [Bug translator/4529] New: tapset coverage option fche at redhat dot com
@ 2007-05-24 20:21 ` wcohen at redhat dot com
  0 siblings, 0 replies; 2+ messages in thread
From: wcohen at redhat dot com @ 2007-05-24 20:21 UTC (permalink / raw)
  To: systemtap


------- Additional Comments From wcohen at redhat dot com  2007-05-24 21:21 -------
Currently there is no information about what parts of the tapset and
scripts are exercised during testing.  Systemtap needs some way
determining what sections of tapsets and scripts are executed.

Code coverage techniques have already been implemented in GCC for
various languages compiled by GCC.

http://gcc.gnu.org/onlinedocs/gcc-4.2.0/gcc/Gcov.html#Gcov

The code coverage of kernel code has also been implemented with
extensions to GCOV:

http://ltp.sourceforge.net/coverage/

The C code compiled with the gcc options (`-fprofile-arcs
-ftest-coverage') writes out information to files (x.gcno). When the
compiled code is run, data is written into x.gcda file. It seems like
systemtap generated code could generate compatible files, so that
analysis could be done lcov.

Where to put the files?
	In the same directory as the original script .stp?

How to deal with the tapsets in separate directories?
	Make use of the GCOV_PREFIX_STRIP and GCOV_PREFIX env variables?

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|systemtap at sources dot    |wcohen at redhat dot com
                   |redhat dot com              |
             Status|NEW                         |ASSIGNED


http://sourceware.org/bugzilla/show_bug.cgi?id=4529

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2007-05-24 20:21 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-05-21 15:46 [Bug translator/4529] New: tapset coverage option fche at redhat dot com
2007-05-24 20:21 ` [Bug translator/4529] " wcohen at redhat dot com

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).