Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:56174
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: <4EB973B2.4040500@anderiasch.de>
Date: Tue, 08 Nov 2011 19:23:46 +0100
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.8.1.23) Gecko/20090812 Lightning/0.9 Thunderbird/2.0.0.23 Mnenhy/0.7.5.0
MIME-Version: 1.0
To: rasmus@lerdorf.com
CC: smalyshev@sugarcrm.com, internals@lists.php.net
References: <4EB8BCC2.6040900@sugarcrm.com> <4EB8F8E2.3010208@anderiasch.de> <4EB904B4.2060504@lerdorf.com> <4EB96A04.2040703@sugarcrm.com> <4EB96B3F.9060705@lerdorf.com>
In-Reply-To: <4EB96B3F.9060705@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 08.11.2011 18:47, Rasmus Lerdorf wrote:
> Valgrind should also have a way to turn off grabbing SIGUSR2. What if
> you are valgrinding something that actually needs it for something real?
> Are you out of luck?

According to the docs this might help:

http://valgrind.org/docs/manual/manual-core.html#manual-core.signals

If you're using signals in clever ways (for example, catching SIGSEGV,
modifying page state and restarting the instruction), you're probably
relying on precise exceptions. In this case, you will need to use
--vex-iropt-precise-memory-exns=yes.

But I've got no access to a mac until tomorrow to test it.

Greetings,
Florian