Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:5849 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 41163 invoked by uid 1010); 1 Dec 2003 06:57:32 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 41139 invoked from network); 1 Dec 2003 06:57:32 -0000 Received: from unknown (HELO shiva.mind.de) (212.42.230.204) by pb1.pair.com with SMTP; 1 Dec 2003 06:57:32 -0000 Received: from [192.168.1.100] (p508EBA05.dip.t-dialin.net [80.142.186.5]) by shiva.mind.de (Postfix) with ESMTP id 0AE2697C6C; Mon, 1 Dec 2003 07:57:26 +0100 (CET) Date: Mon, 1 Dec 2003 07:57:29 +0100 Reply-To: Marcus Boerger X-Priority: 3 (Normal) Message-ID: <19739357875.20031201075729@marcus-boerger.de> To: Markus Fischer Cc: Marcus Boerger , internals@lists.php.net In-Reply-To: <20031130215950.GA14294@gjat.josefine.at> References: <20031129143917.GA11269@gjat.josefine.at> <31603267000.20031129180936@marcus-boerger.de> <20031130215950.GA14294@gjat.josefine.at> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] beta2, deriving from class Extension and calling parent::__toString() segfaults From: helly@php.net (Marcus Boerger) Hello Markus, Sunday, November 30, 2003, 10:59:50 PM, you wrote: > Hi, > On Sat, Nov 29, 2003 at 06:09:36PM +0100, Marcus Boerger wrote : >> this works now. > Thanks. Sorry for the order of reply of the mails, my spam filer > catches this one and I only discovered it yet. >> > Besides the segfaults above, is there a chance we have a nicer HTML >> > formatting for reported Exceptions (while still strip those HTML >> > tags from it for logging)? > Can you advise in this issue too? > The thing is, the stack trace is alright and looks good, but not in > HTML since the line breaks are ordinary ones; there's not HTML > formatting for them, so the line break is not visible in the HTML > output. > If I derive my own exception and override __toString() I can call > nl2br(); but then I've the HTML output in the error_log too. > Seems like an chicken and egg problem. Another solution is to modify > error_prepend/append to encapuslate the error output in a pre block. There you go. > Besides this possible, would it be feasable to handle this issue > right away in PHP for HTML and error log output? Maybe it's not > possible anyway. Hm. I don't think this makes sense but maybe we *could* try to establish a callback into main to display uncaught exceptions. But this must wait until after 5 release i think. -- Best regards, Marcus mailto:helly@php.net