[xdebug-general] Re: Max function call depth for profiling

From: Nathan Nobbe <quickshiftin[@]gmail.com>
Date: Wed, 25 Feb 2015 13:25:05 -0700

Thank you for the hasty response my friend!

On Wed, Feb 25, 2015 at 1:23 PM, Derick Rethans <derick[@]xdebug.org> wrote:

> On Wed, 25 Feb 2015, Nathan Nobbe wrote:
>
> > Hi folks,
> >
> > Is there a limit to the depth of the call stack in the profiling
> > feature of xdebug?
>
> No, there isn't.
>
> > Using PHP Storm as a front end, I can see my_file.php taking over 90%
> > of the time, but the graph doesn't go deep enough in the call tree to
> > see what functions are taking up the time.
>
> I know that kcachegrind doesn't show things if they take up less than 5%
> by default. Perhaps phpstorm does that too?
>
> > I'm able to see what functions are taking up the most time in the
> > execution statistic tab, however it would be nice to see how the code
> > is arriving at the rogue function call.
>
> Difficult to see for me, without profile file, and a pointer as what you
> would expect...
>
> cheers,
> Derick
>
Received on Wed Feb 25 2015 - 20:25:07 GMT

This archive was generated by hypermail 2.2.0 : Mon Jun 25 2018 - 06:00:04 BST