Re: Re: Optional parameter for debug_print_backtrace()

Andi Gutmans wrote:

What else does debug_print_backtrace() include? If the info is more maybe we should change debug_backtrace()? In any case, in general I don't have a problem to do this. Might be nicer if we could do it without output buffering though but I haven't looked at the code to see how hard that would be. Andi At 11:56 PM 3/18/2004 +0100, Andrey Hristov wrote:

Hi internals, what do you think about adding an optional parameter to debug_print_backtrace() (PHP 5 only) so instead of printing the stacktrace to get it as string. The information provided by debug_print_backtrace() is more than the information provided by debug_backtrace(). So if the parameter is added the function will behave just like print_r() which has second optional parameter. I have made a patch which is available here : http://hristov.com/andrey/projects/php_stuff/patches/debug_print_backtrace_as_string.diff.txt Andrey

Hmmm,

looks I was kinda fooled by some script a month ago. I was suprised that with debug_print_backtrace() I was able to see the arguments of the stack since I haven't seen the same done by debug_backtrace(). But few minutes ago I took a look at the code of both functions and they try to extract the arguments from the stack. So this optional parameter to debug_print_backtrace() is not needed. But a question arose, in which cases the arguments from the stack will be extracted and returned?(hope this won't be treated as php-general question ;) ) I tried to simulate something with a small script with no success. Andrey