Re: PHP CLI + Valgrind = FAIL
| From: | Florian Anderiasch | Date: | Tue, 08 Nov 2011 18:23:46 +0000 |
| Subject: | Re: PHP CLI + Valgrind = FAIL | ||
| References: | 1 2 3 4 5 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-56174@lists.php.net to get a copy of this message | ||
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