Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:10548 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 71543 invoked by uid 1010); 16 Jun 2004 22:04:14 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 71519 invoked from network); 16 Jun 2004 22:04:13 -0000 Received: from unknown (HELO secret.deadmime.org) (69.55.224.147) by pb1.pair.com with SMTP; 16 Jun 2004 22:04:13 -0000 Received: from [10.0.1.2] (24.229.134.162.cmts.haz.ptd.net [24.229.134.162]) (authenticated bits=0) by secret.deadmime.org (8.12.11/8.12.11) with ESMTP id i5GM4AHi048188 (version=TLSv1/SSLv3 cipher=EDH-DSS-DES-CBC3-SHA bits=168 verify=NO); Wed, 16 Jun 2004 15:04:12 -0700 (PDT) (envelope-from dank@deadmime.org) In-Reply-To: References: <20040616144748.S26824@secret.deadmime.org> Mime-Version: 1.0 (Apple Message framework v618) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-ID: <17BB1488-BFE1-11D8-8DBC-000A95AD08A8@deadmime.org> Content-Transfer-Encoding: 7bit Cc: php-internals Date: Wed, 16 Jun 2004 18:04:09 -0400 To: OpenMacNews X-Mailer: Apple Mail (2.618) X-Spam-Status: No, hits=0.0 required=7.5 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on secret.deadmime.org Subject: Re: [PHP-DEV] "Segmentation fault" w/ php5.0.0rc3 on macosx10.3.4 From: dank@deadmime.org (Dan Kalowsky) Well if you wish to continue adding more challenges to solving your goal, you could add in the latest CVS versions of gcc as well. Honest, your best bet to start debugging this is to place PHP5+PGPGACL into a stable environment. If it doesn't reproduce there, introduce a semi-stable environment (i.e. any recent Apache2 release). Again if it doesn't reproduce there, move to your extremely volitile setup you've got currently and hope for a chance to attach your debugger to it. Personally, I'd start with the PHP5 cgi/cli and see if it happens there. Easiest way to reproduce and debug the code. On Jun 16, 2004, at 5:56 PM, OpenMacNews wrote: > -- 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