Travis-ci tests fail with valgrind on PHP 7

10 years ago by francois@php.net — view source — reply

unread

Hi Bob,

I'm currently testing a new PHP extension on travis-ci in
valgrind/leak_check mode. In PHP 5 environments, it is OK but, on PHP 7,
every test fails with this message :

valgrind: Bad option: --vex-iropt-register-updates=allregs-at-mem-access

valgrind version is 3.7.0.

For a full log, see https://travis-ci.org/flaupretre/pecl-pcs (hope it's
public. If not ask for the log).

I'm sending this message to you because I see that you did add this
option in run-tests.php some months ago. So, how do you think we can fix
this ? add another test on valgrind version in the script ?

Regards

François

10 years ago by Bob Weinand — view source — reply

unread

Am 10.11.2015 um 04:11 schrieb François Laupretre francois@php.net:

Hi Bob,

I'm currently testing a new PHP extension on travis-ci in valgrind/leak_check mode. In PHP 5 environments, it is OK but, on PHP 7, every test fails with this message :

valgrind: Bad option: --vex-iropt-register-updates=allregs-at-mem-access

valgrind version is 3.7.0.

For a full log, see https://travis-ci.org/flaupretre/pecl-pcs (hope it's public. If not ask for the log).

I'm sending this message to you because I see that you did add this option in run-tests.php some months ago. So, how do you think we can fix this ? add another test on valgrind version in the script ?

Regards

François

Quoting the valgrind 3.8.0 release notes:

Specifically,
--vex-iropt-precise-memory-exns has been removed and replaced by
--vex-iropt-register-updates, with extended functionality.

so, I'll need to update it… may you please verify if --vex-iropt-precise-memory-exns=yes works for you, then I'm going to extend the valgrind version switch appropriately?

Thanks,
Bob

10 years ago by francois@php.net — view source — reply

unread

Le 10/11/2015 04:30, Bob Weinand a écrit :

Quoting the valgrind 3.8.0 release notes:

Specifically,
--vex-iropt-precise-memory-exns has been removed and replaced by
--vex-iropt-register-updates, with extended functionality.

so, I'll need to update it… may you please verify if
--vex-iropt-precise-memory-exns=yes works for you, then I'm going to
extend the valgrind version switch appropriately?

Just added a sed command in my script to modify the option in
run-tests.php before running it, sent it to travis, and it works now.
So, I think you'll have to add another test on the valgrind version
(before/after 3.8.0) and merge this in the 7.0 and master branches.

Regards

François