Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:56158
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain anderiasch.de from 81.169.138.148 cause and error)
Message-ID: <4EB906E1.60601@anderiasch.de>
Date: Tue, 08 Nov 2011 11:39:29 +0100
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: Rasmus Lerdorf <rasmus@lerdorf.com>
CC: Stas Malyshev <smalyshev@sugarcrm.com>, 
 PHP Internals <internals@lists.php.net>
References: <4EB8BCC2.6040900@sugarcrm.com> <4EB8F8E2.3010208@anderiasch.de> <4EB904B4.2060504@lerdorf.com>
In-Reply-To: <4EB904B4.2060504@lerdorf.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] PHP CLI + Valgrind = FAIL
From: ml@anderiasch.de (Florian Anderiasch)

On 11/08/2011 11:30 AM, Rasmus Lerdorf wrote:
> Not deferring SIGUSR2 just because valgrind on OSX doesn't like it isn't
> really an option here. We could make debug builds on OSX not defer it, I
> suppose.

I didn't want to imply we should change PHP behaviour in order to be
valgrindable :)

https://wiki.php.net/rfc/zendsignals is still listed as "Under
discussion", but at least the signals listed under "Startup" are already
registered it seems.

I just learned that the various signals on Linux on Darwin have totally
different numbers than on Linux, but
$ valgrind /bin/bash
shows the same behaviour as PHP, so I suspect it's really valgrind, as
seen in memcheck/tests/sigkill.stderr.exp-darwin,92 in valgrind 3.7 source.

I'm not directly able to see what they're doing different on OS X than
on Linux, and if it makes sense at all - that's for someone with more
expertise in C code review I guess :)

Greetings,
Florian