Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:17740
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
To: Wez Furlong <kingwez@gmail.com>
Cc: internals@lists.php.net
In-Reply-To: <4e89b42605080913403cadb5a5@mail.gmail.com>
References: <1123619893.8518.7.camel@localhost.localdomain>
	<4e89b42605080913403cadb5a5@mail.gmail.com>
Content-Type: text/plain
Date: Tue, 09 Aug 2005 16:44:01 -0400
Message-ID: <1123620241.8518.9.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] GCOV
From: john@coggeshall.org (John Coggeshall)

I also wrote one, i don't care which we use... it's a 5 line shell
script :)

On Tue, 2005-08-09 at 16:40 -0400, Wez Furlong wrote:
> IIRC, we have a script that does this already for our release
> tarballs; should save some effort.
> 
> --Wez.
> 
> On 8/9/05, John Coggeshall <john@coggeshall.org> wrote:
> > Before we deep-freeze the CVS, I'd like to get my GCOV stuff committed.
> > The changes are relatively minor and I've already run it past Andi. I'm
> > trying to get around one last problem that maybe someone else can take
> > care of:
> > 
> > The basic issue is that our parsers have broken file/line preprocessor
> > directives... since we're pre-generating these files and then committing
> > them, things like #file and #line are breaking gcov because it's using
> > them to look for source and the paths are from whomever committed them
> > to begin with. I spoke with Andi about this at OSCON and we agreed that
> > it's probably best when GCOV is enabled to strip those preprocessor
> > directives out beforehand. Any other thoughts/comments? If no one has a
> > better solution I'll commit the code later today.
> > 
> > John
> > 
> > --
> > PHP Internals - PHP Runtime Development Mailing List
> > To unsubscribe, visit: http://www.php.net/unsub.php
> > 
> >
>