Req #47143 [Com]: Throwing an exception in a destructor causes a fatal error
Edit report at http://bugs.php.net/bug.php?id=47143&edit=1
ID: 47143
Comment by: paul at annesley dot cc
Reported by: felixcca at yahoo dot ca
Summary: Throwing an exception in a destructor causes a fatal
error
Status: Closed
Type: Feature/Change Request
Package: *General Issues
Operating System: *
PHP Version: 5.2.8
Assigned To: stas
Block user comment: N
Private report: N
New Comment:
More specifically, this was fixed between PHP 5.3.5 and PHP 5.3.6 in the
following
revision:
------------------------------------------------------------------------
r307523 | stas | 2011-01-17 08:24:43 +1100 (Mon, 17 Jan 2011) | 2 lines
Fix bug #47143, bug #51458 - provide more useful info in bad exception
cases
It didn't seem to make it into the ChangeLog, though.
Previous Comments:
------------------------------------------------------------------------
[2011-01-16 22:26:17] stas@php.net
This bug has been fixed in SVN.
Snapshots of the sources are packaged every three hours; this change
will be in the next snapshot. You can grab the snapshot at
http://snaps.php.net/.
Thank you for the report, and for helping us make PHP better.
------------------------------------------------------------------------
[2011-01-16 22:24:45] stas@php.net
Automatic comment from SVN on behalf of stas
Revision: http://svn.php.net/viewvc/?view=revision&revision=307523
Log: Fix bug #47143, bug #51458 - provide more useful info in bad
exception cases
------------------------------------------------------------------------
[2009-01-18 08:26:28] felixcca at yahoo dot ca
Sorry, made a mistake on the original error message. It's "Exception
thrown without a stack frame," as stated below, and not "Exception
thrown without a stack trace".
------------------------------------------------------------------------
[2009-01-18 05:16:31] felixcca at yahoo dot ca
Description:
------------
Basically a duplicate of #31304, but it seems I can't reopen the ticket
myself since I'm not a dev nor the original poster.
When an exception is thrown in a destructor, the exception is lost, and
a pointless Fatal Error is issued:
Fatal Error: Exception thrown without a stack trace
debug_backtrace() will still get you a stack trace from a destructor
without issuing any error, let alone causing the loss of debugging data.
Also, only wrapping the exception in a try-catch inside the destructor
works, and allows you to just print the exception and exit as if
exceptions really worked in destructors.
Why spit out the Fatal Error?
Reproduce code:
---------------
<?php
class ExceptionThrower
{
public function __destruct()
{
throw new Exception;
}
}
$obj = new ExceptionThrower;
?>
Expected result:
----------------
Fatal error: Uncaught exception 'Exception' in snippet.php:6
Stack trace:
#0 [internal function]: ExceptionThrower->__destruct()
#1 {main}
thrown in snippet.php on line 6
Actual result:
--------------
Fatal error: Exception thrown without a stack frame in Unknown on line 0
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/bug.php?id=47143&edit=1
Thread (4 messages)