#26750 [Opn->Fbk]: backtrace crash server
| From: | sniper@php.net | Date: | Fri, 02 Jan 2004 15:28:55 +0000 |
| Subject: | #26750 [Opn->Fbk]: backtrace crash server | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-52711@lists.php.net to get a copy of this message | ||
ID: 26750
Updated by: sniper@php.net
Reported By: php dot bug at stre dot it
-Status: Open
+Status: Feedback
Bug Type: Zend Engine 2 problem
Operating System: win32 nt5.1
PHP Version: 5.0.0b3 (beta3)
New Comment:
Thank you for this bug report. To properly diagnose the problem, we
need a short but complete example script to be able to reproduce
this bug ourselves.
A proper reproducing script starts with <?php and ends with ?>,
is max. 10-20 lines long and does not require any external
resources such as databases, etc.
If possible, make the script source available online and provide
an URL to it here. Try avoid embedding huge scripts into the report.
Previous Comments:
------------------------------------------------------------------------
[2003-12-30 21:42:55] php dot bug at stre dot it
Description:
------------
this failure happens not in every context, i cant reproduce the concret
context it happens (to much code).
but something to the context:
i have a abstract class (PageException) extending Exception
in this class i call the function debug_backtrace inside the
constructor.
The pageexception class is super class of ExpressionException
the expressionexception will be throw in a page included inside a
method of a object
when i call the function debug_backtrace php dont come out of the
function and the page ends with a timeout (infinity loop?). when i
remove debug_backtrace everything is ok.
in the same context the function debug_print_backtrace apache webserver
throw a failure looks like bad reference (the instruction at
"0x100dfc8b" referenced memory at "0x00000000". the memory could not be
"read")
Reproduce code:
---------------
sorry to much
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=26750&edit=1