refine last patch. if the argument-stack is not consistent don't try to show
arguments. no call to zend_error is made as we might end up in an infinite
recursion if called from an error_handl

refine last patch. if the argument-stack is not consistent don't try to show
arguments. no call to zend_error is made as we might end up in an infinite
recursion if called from an error_handler.
so: if the arguments to functions aren't shown in debug_backtrace this is 'cause
the arument stack was not consistent when debug_backtrace was called.

show more ...

debug_backtrace() now checks the complete argument-stack for consistency.

debug_backtrace()
- make args passed to functions called vy call_user_function available again.

debug_backtrace():
- make args work if called from the error_handler
- fix refcount for args

debug_backtrace(): show name of included file for include and require calls
plus some small fixes suggested by andi.
# now it's perfect;-)

- Whitespace

- Whitespace and better variable name

fix warning

debug_backtrace: show include/require/eval as normal functions on the stack
# the hard bit is to find out the args for those

- No spaces :)

- debug_backtrace now also returns an array containing the arguments of the
called function.

zeev, andi - is knowing the structure of the stack considered a bad thing in
zend_built

- debug_backtrace now also returns an array containing the arguments of the
called function.

zeev, andi - is knowing the structure of the stack considered a bad thing in
zend_builtin_function? if yes i would have to create a new function in
zend_ptr_stack.c (but i think we are save this way)

show more ...

- debug_backtrace:
added "type" ('->' or '::') for object calls.
made calls done thru call_user_func show-up correct in backtraces.

andi,
does this look correct t

- debug_backtrace:
added "type" ('->' or '::') for object calls.
made calls done thru call_user_func show-up correct in backtraces.

andi,
does this look correct to you?

show more ...

@- Added set_exception_handler() function for registering a global,
@ catch-all exception handling function (Stig)
- Added set_exception_handler() function for registering a global,
ca

@- Added set_exception_handler() function for registering a global,
@ catch-all exception handling function (Stig)
- Added set_exception_handler() function for registering a global,
catch-all exception handling function (Stig)

show more ...

- Fix problem with debug_backtrace() reported by Stig. We weren't reporting
- global function information because it wasn't available. We have to do
- an additional assignment per-function ca

- Fix problem with debug_backtrace() reported by Stig. We weren't reporting
- global function information because it wasn't available. We have to do
- an additional assignment per-function call so that it'll be available.
- Also don't define the global scope as function name _main_ but leave it
- empty so that frameworks like Pear can decide what they want to do.

show more ...

* folding fixes

- Centralize global class fetch

- Don't show debug_backtrace() in the trace itself.
- This patch is a bit ugly because the whole code itself is pretty complex
- and hard to re-order.

only check for an available class entry instead of
the std_object_handlers on some places

#some linuxtag work

- MFZE1

- Nuke C++ comment

- Make debug_backtrace() return an array. Still not finished because I
might want to differentiate between method calls and static methods.

Example:
$bt = debug_backtrace();
fore

- Make debug_backtrace() return an array. Still not finished because I
might want to differentiate between method calls and static methods.

Example:
$bt = debug_backtrace();
foreach ($bt as $frame) {
if (isset($frame['class'])) {
print $frame['class'];
print "::";
}
print $frame['function'];
print " [";
print $frame['file'];
print ":";
print $frame['line'];
print "]\n";
}

show more ...

- Hopefully fix problems with debug_backtrace()

- MFZE1

- More debug backtrace work. It still doesn't work very well...

Initial support for built-in backtracing.
There are still a few problems such as includes and calling other functions
from internal functions which aren't seen (will have to think if and how

Initial support for built-in backtracing.
There are still a few problems such as includes and calling other functions
from internal functions which aren't seen (will have to think if and how to
fix this).
Also the main scripts filename isn't available. Need to think about that.

show more ...