Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:36668 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 9428 invoked from network); 29 Mar 2008 01:36:50 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 29 Mar 2008 01:36:50 -0000 Authentication-Results: pb1.pair.com smtp.mail=scott@macvicar.net; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=scott@macvicar.net; sender-id=unknown Received-SPF: error (pb1.pair.com: domain macvicar.net from 72.232.140.210 cause and error) X-PHP-List-Original-Sender: scott@macvicar.net X-Host-Fingerprint: 72.232.140.210 midden.org.uk Received: from [72.232.140.210] ([72.232.140.210:50826] helo=lovelace.midden.org.uk) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 60/C5-25926-F2D9DE74 for ; Fri, 28 Mar 2008 20:36:48 -0500 Received: from macvicar.demon.co.uk ([80.177.111.173] helo=[192.168.1.101]) by lovelace.midden.org.uk with esmtpsa (TLS-1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.63) (envelope-from ) id 1JfPzw-0008Hs-L2; Sat, 29 Mar 2008 01:36:45 +0000 Cc: PHP Developers Mailing List Message-ID: <17ADB92D-0D73-41CB-8776-EEC3D44A1105@macvicar.net> To: Jeremy Privett In-Reply-To: <47ED9763.4070908@omegavortex.net> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v919.2) Date: Sat, 29 Mar 2008 01:36:35 +0000 References: <47ED9763.4070908@omegavortex.net> X-Mailer: Apple Mail (2.919.2) Subject: Re: [PHP-DEV] Exceptions = Apache Crash in PHP 5.3 Snaps From: scott@macvicar.net (Scott MacVicar) Can you try a debug build with --enable-debug to get a more detailed backtrace. Also what is the exact configure line and which apache 2 model are you using? Worker or Pre-fork? Scott On 29 Mar 2008, at 01:12, Jeremy Privett wrote: > Hey list, > > I really /really/ hate to cause additional noise on this list, but > I'm developing software in the PHP 5.3 snapshots with a timeline for > release around the same time this version of PHP is released. We > always try to keep current with our snapshots to make sure > everything still works. My development team has been grinded almost > to a halt by the fact that any thrown exception in the latest PHP > 5.3 snapshots is causing Apache to crash. > > There's already a bug report here: http://bugs.php.net/bug.php? > id=44226 > > I know unreleased PHP versions can't be supported, but fundamental > language functionality was broken. This bug has been open for a > month. This seems like it would be a critical problem and I'm glad > Jani had already looked at and responded to the report. This is just > slowing my team down when the snapshots are generally pretty high > quality, from my personal experience. If this could be looked at > further, I would gladly help someone with debugging and testing and > such, if they'll take a look at the code. > > Thanks. > > -- > Jeremy Privett > C.E.O. & C.S.A. > Omega Vortex Corporation > > http://www.omegavortex.net > > Please note: This message has been sent with information that could > be confidential and meant only for the intended recipient. If you > are not the intended recipient, please delete all copies and inform > us of the error as soon as possible. Thank you for your cooperation. >