From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10680 invoked by alias); 27 Jun 2005 15:05:53 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 10667 invoked by uid 22791); 27 Jun 2005 15:05:48 -0000 Received: from relay02.pair.com (HELO relay02.pair.com) (209.68.5.16) by sourceware.org (qpsmtpd/0.30-dev) with SMTP; Mon, 27 Jun 2005 15:05:48 +0000 Received: (qmail 63308 invoked from network); 27 Jun 2005 15:05:47 -0000 Received: from unknown (HELO ?192.168.123.1?) (unknown) by unknown with SMTP; 27 Jun 2005 15:05:47 -0000 X-pair-Authenticated: 24.126.76.52 Message-ID: <42C013F6.9080208@kegel.com> Date: Mon, 27 Jun 2005 15:05:00 -0000 From: Dan Kegel User-Agent: Mozilla/4.0 (compatible;MSIE 5.5; Windows 98) MIME-Version: 1.0 To: GCC Mailing List , ransom@cs.pdx.edu, gcov-capstone@cs.pdx.edu Subject: re: [RFC] gcov tool, comparing coverage across platforms Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2005-06/txt/msg01053.txt.bz2 > We are a group of undergrads at Portland State University who accepted as our senior capstone software engineering project a proposed tool for use with gcov for summarizing gcov outputs for a given piece of source code tested on multiple architecture/OS platforms. A summary of the initial proposal is here: > http://www.clutchplate.org/gcov/gcov_proposal.txt > > A rough overview of our proposed design is as follows: > We would build a tool which would accept as input: > on the command line, paths to each .gcov file to be included in the summary, > each of these to be followed by a string which would be the platform identifier for > that .gcov file. > The .gcov files would be combined so that the format would parallel the existing output, > with the summarized report listing each line of the source once, followed immediately > by a line for each platform id and the coverage data for that platform. Sounds like a fun project. Rather than taking the path to each .gcov file on the commandline, you might consider searching from them, as lcov does. Come to think of it, maybe you could steal some ideas or even code from lcov. See http://ltp.sourceforge.net/coverage/lcov.php ltp is written in perl, for what it's worth. I like using Bourne shell for projects it's a good fit for, but you may find yourself needing something like perl, since you'll be wrangling lots of files and lots of text. - Dan -- Trying to get a job as a c++ developer? See http://kegel.com/academy/getting-hired.html