On 04/04/2011 07:37 PM, Patrick ALLAERT wrote:
I would then add the same option to debug_print_backtrace().
Not sure I want to touch debug_print_backtrace() as it does not use
zend_fetch_debug_backtrace().
It could also make sense to test it with a limit greater than the
actual depth.
Th
Good idea. Have you considered how Xdebug does this kind of thing (through
configuration directives, IIRC--I know it uses such things for var_dump) and
whether that might suggest a better or more future-proof approach?
Ben.
On 5/04/11 1:22 AM, Sebastian Bergmann wrote:
https://gist.github.c
2011/4/4 Sebastian Bergmann :
> https://gist.github.com/901579 is a patch against trunk that adds an
> optional $limit argument to debug_backtrace() to limit the number of
> frames returned.
>
> Any thoughts?
I would then add the same option to debug_print_backtrace().
It could also make sens
https://gist.github.com/901579 is a patch against trunk that adds an
optional $limit argument to debug_backtrace() to limit the number of
frames returned.
Any thoughts?
--
Sebastian BergmannCo-Founder and Principal Consultant
http://sebastian-bergmann.de/
