Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:39647 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 278 invoked from network); 5 Aug 2008 00:50:13 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 5 Aug 2008 00:50:13 -0000 Authentication-Results: pb1.pair.com smtp.mail=andrei@gravitonic.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=andrei@gravitonic.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain gravitonic.com from 209.85.146.182 cause and error) X-PHP-List-Original-Sender: andrei@gravitonic.com X-Host-Fingerprint: 209.85.146.182 wa-out-1112.google.com Received: from [209.85.146.182] ([209.85.146.182:2753] helo=wa-out-1112.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B2/F3-12766-3C3A7984 for ; Mon, 04 Aug 2008 20:50:12 -0400 Received: by wa-out-1112.google.com with SMTP id v27so1530764wah.17 for ; Mon, 04 Aug 2008 17:50:09 -0700 (PDT) Received: by 10.115.15.5 with SMTP id s5mr15165233wai.6.1217897408826; Mon, 04 Aug 2008 17:50:08 -0700 (PDT) Received: from Macintosh-18.local ( [71.202.45.81]) by mx.google.com with ESMTPS id m28sm12267528poh.10.2008.08.04.17.50.06 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 04 Aug 2008 17:50:07 -0700 (PDT) Message-ID: <4897A3BD.8090604@gravitonic.com> Date: Mon, 04 Aug 2008 17:50:05 -0700 User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070807) MIME-Version: 1.0 To: Ian Eure CC: PHP Developers Mailing List References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] socket_select() problem From: andrei@gravitonic.com (Andrei Zmievski) Ian Eure wrote: > I wrote a simple testcase that submits a single job to Gearman. If I run > it under Apache2, I get the socket_select() warning. If I run it from > the CLI, I don't. I'm also pointing the CLI at the Apache2 php.ini file. > At this point, I don't know how to track this any further. If I was > getting the same error on the CLI, I could trace it with gdb. I don't > know how I'd go about doing something like that for an Apache extension. A really quick answer to this part: If you want to trace this with gdb run Apache2, stop apache processes, then run apache under gdb like this: % sudo gdb apache2 > run -X You can set the breakpoint before "run -X" or after it finishes loading by stopping it with Ctrl-C, setting breakpoint, and cont'inuing. -X ensures that it runs only a single process. -Andrei