Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:56171 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 98491 invoked from network); 8 Nov 2011 17:42:31 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 8 Nov 2011 17:42:31 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 67.192.241.143 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 67.192.241.143 smtp143.dfw.emailsrvr.com Linux 2.6 Received: from [67.192.241.143] ([67.192.241.143:57305] helo=smtp143.dfw.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id FE/F0-28203-70A69BE4 for ; Tue, 08 Nov 2011 12:42:31 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp24.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id DF22C180489; Tue, 8 Nov 2011 12:42:28 -0500 (EST) X-Virus-Scanned: OK Received: by smtp24.relay.dfw1a.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 9DD90180118; Tue, 8 Nov 2011 12:42:28 -0500 (EST) Message-ID: <4EB96A04.2040703@sugarcrm.com> Date: Tue, 08 Nov 2011 09:42:28 -0800 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 MIME-Version: 1.0 To: Rasmus Lerdorf CC: PHP Internals 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; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] PHP CLI + Valgrind = FAIL From: smalyshev@sugarcrm.com (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 defer it, I > suppose. Why it isn't an option? I.e. suppose by some reason - valgrind, debugger, profiler, etc. - sigaction fails and we can't defer certain signals. 99.9% of cases of running PHP never need it, why we much have E_ERROR in this case? I understand that removing the override altogether would be pointless, but why we can't just avoid hard failure there? Would anything break (except theoretical race condition) there? -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227