Re: [PHP-DEV] PHP CLI + Valgrind = FAIL

2011-11-08 Thread Yasuo Ohgaki
2011/11/9 Rasmus Lerdorf : > I think it is a new thing in Valgrind 3.7 When I upgraded from Leopard to Snow Leopard, I couldn't use valgrind for a while. It was some kind of startup problem. Good to know if there is problem with newer version. This is one reason that I'm holding upgrade to Lion. (

Re: [PHP-DEV] PHP CLI + Valgrind = FAIL

2011-11-08 Thread Rasmus Lerdorf
I think it is a new thing in Valgrind 3.7 On 11/08/2011 02:23 PM, Yasuo Ohgaki wrote: > Hi Stats, > > New gmail's, wordwrap and message display/sync, is killing me... > > Anyway, I've been using valgrind on my osx 10.6 with PHP 5.3 for a > while and I don't have startup problem with PHP 5.4 like

Re: [PHP-DEV] PHP CLI + Valgrind = FAIL

2011-11-08 Thread Yasuo Ohgaki
Hi Stats, New gmail's, wordwrap and message display/sync, is killing me... Anyway, I've been using valgrind on my osx 10.6 with PHP 5.3 for a while and I don't have startup problem with PHP 5.4 like you did. It sounds like valgrind configuration is different or osx version differs. I'm using yoh

Re: [PHP-DEV] PHP CLI + Valgrind = FAIL

2011-11-08 Thread 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.h

Re: [PHP-DEV] PHP CLI + Valgrind = FAIL

2011-11-08 Thread Rasmus Lerdorf
On 11/08/2011 09:42 AM, Stas Malyshev wrote: > Hi! > >> On 11/08/2011 01:39 AM, Florian Anderiasch wrote: >>> So it looks like only FPM uses it for more than the default behaviour of >>> "terminate", from a quick glance. >> Not deferring SIGUSR2 just because valgrind on OSX doesn't like it isn't >

Re: [PHP-DEV] PHP CLI + Valgrind = FAIL

2011-11-08 Thread Stas Malyshev
Hi! On 11/08/2011 01:39 AM, Florian Anderiasch wrote: So it looks like only FPM uses it for more than the default behaviour of "terminate", from a quick glance. 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

Re: [PHP-DEV] PHP CLI + Valgrind = FAIL

2011-11-08 Thread Stas Malyshev
Hi! On 11/8/11 1:34 AM, Yasuo Ohgaki wrote: It seems copy&paste from a message don't work well. Try running some script, not -v. IIRC -v doesn't initialize request. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227 -- PHP Internals - PHP Runt

Re: [PHP-DEV] PHP CLI + Valgrind = FAIL

2011-11-08 Thread Florian Anderiasch
On 11/08/2011 10:34 AM, Yasuo Ohgaki wrote: > yohgaki@esi-yasmc1$ USE_ZEND_ALLOC=0 valgrind ./sapi/cli/php -v > ==63465== Memcheck, a memory error detector > ==63465== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et al. > ==63465== Using Valgrind-3.6.1 and LibVEX; rerun with -h for copy

Re: [PHP-DEV] PHP CLI + Valgrind = FAIL

2011-11-08 Thread Yasuo Ohgaki
On Tue, Nov 8, 2011 at 7:54 PM, Yasuo Ohgaki wrote: > I've been using valgrind with PHP 5.3 for sometime on my osx, and > didn't have problem. > As I just pasted the result with PHP 5.4, it seems working with my > configuration. > > My MacPorts was old enough, so I'm currently updating to latest >

Re: [PHP-DEV] PHP CLI + Valgrind = FAIL

2011-11-08 Thread Yasuo Ohgaki
On Tue, Nov 8, 2011 at 7:39 PM, Florian Anderiasch wrote: > 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 w

Re: [PHP-DEV] PHP CLI + Valgrind = FAIL

2011-11-08 Thread 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

Re: [PHP-DEV] PHP CLI + Valgrind = FAIL

2011-11-08 Thread Rasmus Lerdorf
On 11/08/2011 01:39 AM, Florian Anderiasch wrote: > So it looks like only FPM uses it for more than the default behaviour of > "terminate", from a quick glance. Well, it is part of the new 5.4 signal handling code that defers these signals, including SIGUSR2, when inside a critical section. In ord

Re: [PHP-DEV] PHP CLI + Valgrind = FAIL

2011-11-08 Thread Florian Anderiasch
On 11/08/2011 06:23 AM, Stas Malyshev wrote: > Indeed, valgrind says: > ==47112== Warning: ignored attempt to set SIGUSR2 handler in sigaction(); > ==47112== the SIGUSR2 signal is used internally by Valgrind > > So it looks like it won't allow PHP to override signal handlers. The > questi

Re: [PHP-DEV] PHP CLI + Valgrind = FAIL

2011-11-08 Thread Yasuo Ohgaki
It seems copy&paste from a message don't work well. yohgaki@esi-yasmc1$ uname -a Darwin esi-yasmc1.esi.local 10.8.0 Darwin Kernel Version 10.8.0: Tue Jun  7 16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386 i386 yohgaki@esi-yasmc1$ ./sapi/cli/php -v PHP 5.4.0RC1-dev (cli) (built: Nov  8 2011 1

Re: [PHP-DEV] PHP CLI + Valgrind = FAIL

2011-11-08 Thread Yasuo Ohgaki
Sorry I replied to wrong thread. I haven't used to new gmail UI... It seems working on my MacBook.I just tried php-src-5.4 with $ uname -aDarwin esi-yasmc1.esi.local 10.8.0 Darwin Kernel Version 10.8.0: TueJun  7 16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386 i386$./configure && make and go

Re: [PHP-DEV] PHP CLI + Valgrind = FAIL

2011-11-08 Thread Antony Dovgal
On 11/08/2011 10:43 AM, Rasmus Lerdorf wrote: Indeed, valgrind says: ==47112== Warning: ignored attempt to set SIGUSR2 handler in sigaction(); ==47112== the SIGUSR2 signal is used internally by Valgrind So it looks like it won't allow PHP to override signal handlers. The questions

Re: [PHP-DEV] PHP CLI + Valgrind = FAIL

2011-11-07 Thread Rasmus Lerdorf
On 11/07/2011 09:23 PM, Stas Malyshev wrote: > Hi! > > I've noticed that if I run PHP 5.4 under Valgrind on my Mac, I get this: > > Fatal error: Error installing signal handler for 31 in Unknown on line 0 > Could not startup. > > Indeed, valgrind says: > ==47112== Warning: ignored attempt to set