Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:64563 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 12981 invoked from network); 5 Jan 2013 22:31:00 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 5 Jan 2013 22:31:00 -0000 Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 173.203.6.155 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 173.203.6.155 smtp155.ord.emailsrvr.com Linux 2.6 Received: from [173.203.6.155] ([173.203.6.155:42084] helo=smtp155.ord.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C2/39-62408-2A9A8E05 for ; Sat, 05 Jan 2013 17:30:59 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp12.relay.ord1a.emailsrvr.com (SMTP Server) with ESMTP id 34C602E0093; Sat, 5 Jan 2013 17:30:56 -0500 (EST) X-Virus-Scanned: OK Received: by smtp12.relay.ord1a.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id CB90F2E008B; Sat, 5 Jan 2013 17:30:55 -0500 (EST) Message-ID: <50E8A99F.5000900@sugarcrm.com> Date: Sat, 05 Jan 2013 14:30:55 -0800 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: =?UTF-8?B?SsOhY2h5bSBUb3XFoWVr?= CC: "internals@lists.php.net" References: <50E742A7.9010909@sugarcrm.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] How to get a PHP bug fixed? From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > I've looked into it and I'm not sure whether an option for getTrace > method is the best way to solve this. I mean the trace is created > along with the exception so it would have to be generated with the > object fields regardless and then filtered if the option is not set. > I think it would be better to add new PHP directive for this > (disabled by default for back compatibility). No, I don't think it is a good idea. We have too many config directives already, and behavior-modifying directives is really not a good idea, since it is a global state with all its problems. > Also what do you mean by DEBUG_BACKTRACE_*? Constants used for trace parameters. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227