From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27579 invoked by alias); 24 May 2007 20:21:37 -0000 Received: (qmail 27492 invoked by uid 48); 24 May 2007 20:21:09 -0000 Date: Thu, 24 May 2007 20:21:00 -0000 Message-ID: <20070524202109.27491.qmail@sourceware.org> From: "wcohen at redhat dot com" To: systemtap@sources.redhat.com In-Reply-To: <20070521164611.4529.fche@redhat.com> References: <20070521164611.4529.fche@redhat.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug translator/4529] tapset coverage option X-Bugzilla-Reason: AssignedTo Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2007-q2/txt/msg00393.txt.bz2 ------- 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.