Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:56148 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 22539 invoked from network); 8 Nov 2011 09:00:50 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 8 Nov 2011 09:00:50 -0000 Authentication-Results: pb1.pair.com smtp.mail=tony@daylessday.org; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=tony@daylessday.org; sender-id=pass Received-SPF: pass (pb1.pair.com: domain daylessday.org designates 95.163.84.66 as permitted sender) X-PHP-List-Original-Sender: tony@daylessday.org X-Host-Fingerprint: 95.163.84.66 mail.daylessday.org Received: from [95.163.84.66] ([95.163.84.66:50576] helo=daylessday.org) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 60/80-20122-0CFE8BE4 for ; Tue, 08 Nov 2011 04:00:49 -0500 Received: from thinkx201.site (unknown [212.42.62.198]) by daylessday.org (Postfix) with ESMTPSA id BD8E1E35F0 for ; Tue, 8 Nov 2011 13:00:45 +0400 (MSK) Message-ID: <4EB8EFBD.1030509@daylessday.org> Date: Tue, 08 Nov 2011 13:00:45 +0400 User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.23) Gecko/20110920 SUSE/3.1.15 Lightning/1.0b3pre Thunderbird/3.1.15 MIME-Version: 1.0 To: internals@lists.php.net References: <4EB8BCC2.6040900@sugarcrm.com> <4EB8CFA7.3090804@lerdorf.com> In-Reply-To: <4EB8CFA7.3090804@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: tony@daylessday.org (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 here are - does anybody sees same problem (on Mac or other >> systems) and should PHP really fail in this scenario? Not having the >> possibility to run PHP under valgrind kind of sucks. Yeah, definitely looks like some Valgrind + OSX problem. I use Valgrind with PHP for years on Linux 32bit/64bit and it works just perfectly. Mine is 3.6.1, too. -- Wbr, Antony Dovgal --- http://pinba.org - realtime profiling for PHP