Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:30375
Return-Path: <jakob.buchgraber@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 4678 invoked by uid 1010); 30 Jun 2007 14:15:22 -0000
Delivered-To: ezmlm-scan-internals@lists.php.net
Delivered-To: ezmlm-internals@lists.php.net
Received: (qmail 4663 invoked from network); 30 Jun 2007 14:15:22 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 30 Jun 2007 14:15:22 -0000
X-Host-Fingerprint: 193.170.68.74 unknown  
Received: from [193.170.68.74] ([193.170.68.74:18859] helo=localhost.localdomain)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id E3/91-24942-77566864 for <internals@lists.php.net>; Sat, 30 Jun 2007 10:15:20 -0400
Message-ID: <E3.91.24942.77566864@pb1.pair.com>
To: internals@lists.php.net
Date: Sat, 30 Jun 2007 16:15:16 +0200
User-Agent: Thunderbird 2.0.0.0 (X11/20070326)
MIME-Version: 1.0
References: <34.E2.21924.65914864@pb1.pair.com>	<20070628150143.028d46f5@localhost> <20070630093118.fbiio9bu8sgcskks@webmail.cernun.net>
In-Reply-To: <20070630093118.fbiio9bu8sgcskks@webmail.cernun.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Posted-By: 193.170.68.74
Subject: Re: [PHP-DEV] Re: Exception thrown without a stack frame
From: jakob.buchgraber@gmail.com (Jakob Buchgraber)

Adam Ashley wrote:
>>> I sometimes get the following error
>>>  >> <b>Fatal error</b>:  Exception thrown without a stack frame in
>>>  >> <b>Unknown</b> on line <b>0</b><br />
>>>
>>> What does this mean?
>>
>> When we see these, they're typically from our custom session handler.
>>
> 
> In my experience that error is almost certainly in a piece of your code 
> that is run after the main execution of the program is complete. So 
> places to check are shutdown functions (things registered with 
> register_shutdown_function()), custom session handlers and object 
> destructors. Basically any piece of code that can be called after the 
> official execution of your script is complete and clean-up is occuring.
> 
> Adam Ashley

Yes that's right. This error occured in my Logger class as all the 
messages are written into a buffer and when the destructor is called the 
data in the buffer are written into a file.
Is that a bad solution? Any alternatives?

Thank you!

Jay