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
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