Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:94730
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain siobud.com designates 104.236.58.159 as permitted sender)
Date: Wed, 27 Jul 2016 17:22:24 -0500
To: Adam Baratz <adam.baratz@gmail.com>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Message-ID: <20160727222224.GA1171@SeanLaptop.siobud.com>
References: <CADxrgCOUNodLGB=42XVuBwCbL1TEXTKhujhJ+9OUsQZQgmwkFQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CADxrgCOUNodLGB=42XVuBwCbL1TEXTKhujhJ+9OUsQZQgmwkFQ@mail.gmail.com>
User-Agent: Mutt/1.6.0 (2016-04-01)
Subject: Re: [PHP-DEV] automating gcov with third-party extensions
From: sean@siobud.com (Sean DuBois)

On Wed, Jul 27, 2016 at 05:22:24PM -0400, Adam Baratz wrote:
> I had a positive experience using gcov with a C extension. I used it to get
> a better sense of what the .phpt tests (and valgrind) were really telling
> me.
>
> To get it to work in an automated way, I hacked out Makefile.gcov and some
> relevant chunks of config.m4 from php-src. I'm wondering if there would be
> value in getting phpize to produce some of this. Am I right in guessing
> that other people want to do things like this?
>
> Thanks,
> Adam

Hey Adam!

It was a pain, but I managed to get gcov running without making any
changes to build stuff. The most important stuff was EXTRA_LDFLAGS so
the build process wouldn't blow away the gcno
https://github.com/php/pecl-math-stats/blob/master/.travis.yml

The I ship it off to a third party service, which gives really nice
visualizations. When bugs hit is gives a quick way to guesstimate where
they are.
https://codecov.io/gh/Sean-Der/pecl-mail-mailparse/src/php7/php_mailparse_mime.c