Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:64597 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 76878 invoked from network); 6 Jan 2013 04:16:33 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Jan 2013 04:16:33 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 67.192.241.133 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 67.192.241.133 smtp133.dfw.emailsrvr.com Linux 2.6 Received: from [67.192.241.133] ([67.192.241.133:39885] helo=smtp133.dfw.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 49/C5-62408-F9AF8E05 for ; Sat, 05 Jan 2013 23:16:32 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp13.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id 60DF53D0293; Sat, 5 Jan 2013 23:16:28 -0500 (EST) X-Virus-Scanned: OK Received: by smtp13.relay.dfw1a.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id C2E323D0146; Sat, 5 Jan 2013 23:16:27 -0500 (EST) Message-ID: <50E8FA90.7030507@sugarcrm.com> Date: Sat, 05 Jan 2013 20:16:16 -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> <50E8A99F.5000900@sugarcrm.com> <50E8BA82.5000700@sugarcrm.com> <50E8BC3E.4030705@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 agree with you that the parameters would be good. There should also > be the limit parameter (same as for debug_backtrace). However I'm > afraid I'm not that much familiar with C to actually write it. There's a bigger problem with this bug. The problem is that if we keep the object in the exception, we may break some other things. See this bug: https://bugs.php.net/bug.php?id=29368 The fix for it relies on the fact that if ctor fails, nobody holds the reference to the object. In the case when we keep the object, this no longer would be true and this bug would show up again. So before we change this, we need better solution for #29368. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227