It would be really helpful to have sort of a callstack log capability where one could see when and where each item was pushed or popped from the stack. Maybe even an external txt file log rather than another interface to clutter up the screen.

The other wish would be to have the call stack not erase the stack on a remote debug failure. There was a strange require_once call that caused the debugger to terminate abruptly because of a bad map nested in a sub-class of the code that could have been easily discovered if I had access to the stack view at the time of failure.

Thanks!

interestingly enough.
Could you post there a sample of code(s) that would replicate the problem ?
Also, please include some info about what dbg versions was used, what php version, what server platform etc.