In August I mostly spent my time on improving Xdebug's xdebug_get_function_stack() function and stack traces with regard to chained exceptions. A feature request asked whether it would be possible to add the local variables for each stack frame that is returned with the xdebug_get_function_stack() function. Xdebug can already show local variables for the top most frame when it shows stack traces (through the xdebug.show_local_vars setting), but the function's result don't include them. When implementing this feature, I noticed that arguments were being returned as strings, instead of actual values, as part of each stack frame. However, at that stage, the original stack has been destroyed, and Xdebug no longer could access that information.