Re: How to trace a crash bug?
| From: | Ferenc Kovacs | Date: | Sat, 27 Mar 2010 12:09:55 +0000 |
| Subject: | Re: How to trace a crash bug? | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-47652@lists.php.net to get a copy of this message | ||
On Sat, Mar 27, 2010 at 11:00 AM, Alexey Zakhlestin <indeyets@gmail.com>wrote:
>
> On 27.03.2010, at 9:05, Thomas Hruska wrote:
>
> > One thought: Has a way to track call depth been considered (perhaps
> _execute())? If the number of calls exceeds a certain (reasonable) number,
> a warning or notice could be displayed and the output buffer flushed. That
> way, when it crashes, there is a log of some sort for the function. Then
> again, I don't know Zend well enough to make that sort of judgment call and
> such a thing could affect performance.
>
> XDebug can do this.
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
> And suhosin can prevent infininte recursion (bailing out with a fatal error
instead of segfault).
We had a discussion with Pierre that this(maximum recursion limit) should be
in the core or not.
Tyrael