Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:15287
Return-Path: <cellog@php.net>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 62071 invoked by uid 1010); 6 Mar 2005 15:38:30 -0000
Delivered-To: ezmlm-scan-internals@lists.php.net
Delivered-To: ezmlm-internals@lists.php.net
Received: (qmail 62046 invoked by uid 1007); 6 Mar 2005 15:38:30 -0000
Message-ID: <20050306153830.62045.qmail@lists.php.net>
To: internals@lists.php.net
Date: Sun, 06 Mar 2005 10:38:30 -0500
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Posted-By: 66.65.39.8
Subject: assistance with segfaults in debug_backtrace()
From: cellog@php.net (Greg Beaver)

Hi,

We're getting quite a few reports of PEAR segfaulting on a 
debug_backtrace() call found in the constructor of PEAR_Error.  Jan 
Schneider reported that it seemed to occur when one of the methods in 
the trace happened in a file that the uid did not have write access to 
(i.e. a PEAR file installed by root), but Davey Shafik posted a report 
that it happened to him while running "pear upgrade PEAR" as root.  He 
also posted a backtrace that might be useful at:

http://pear.php.net/bugs/bug.php?id=3683

Any tips on how to proceed in isolating this?  I can't reproduce the 
problem on any of my systems (windows xp, gentoo).

Greg