Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:10546 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 45959 invoked by uid 1010); 16 Jun 2004 21:56:17 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 45885 invoked from network); 16 Jun 2004 21:56:16 -0000 Received: from unknown (HELO mail1.speakeasy.net) (216.254.0.201) by pb1.pair.com with SMTP; 16 Jun 2004 21:56:16 -0000 Received: (qmail 18313 invoked from network); 16 Jun 2004 21:56:16 -0000 Received: from ns1.presence-group.net (HELO [172.30.11.6]) (blakers@[216.27.177.134]) (envelope-sender ) by mail1.speakeasy.net (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 16 Jun 2004 21:56:16 -0000 Date: Wed, 16 Jun 2004 14:56:14 -0700 Reply-To: OpenMacNews To: php-internals cc: Dan Kalowsky Message-ID: In-Reply-To: <20040616144748.S26824@secret.deadmime.org> References: <20040616144748.S26824@secret.deadmime.org> X-Mailer: Mulberry/3.1.5 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Re: [PHP-DEV] "Segmentation fault" w/ php5.0.0rc3 on macosx10.3.4 From: php-dev.20.openmacnews@spamgourmet.com (OpenMacNews) -- On Wednesday, June 16, 2004 2:49 PM -0700 Dan Kalowsky wrote: > A good start would be to move away from a completely developer environment like you're using. I'd suggest either working with PHP5 or Apache2-dev, but not both at the same time. That should help you narrow things down a bit more. In reality, I'd narrow to Apache1 as well if you're trying to debug some bit of code in PHP. fair point, but its exactly this "manybody" developer environment i'm trying to debug. i've had do other probs (so far ...) w/ the setup i'm using. if seems that something in the phpgacl 'stuff' is causing php5+apache to choke ... the question -- for me -- is HOW to track down WHAT the issue is. that said, THIS problem is reproducible with apache 2.0.49 as well ... richard