>>>>I am new to xdebug, already having some auto profiling outputs (txt
>>>>files). Is it possible to visualize this somehow, or do I need the
>>>>latest CVS version of xdebug to generate output ready for some
>>>>visualization tool?
>>>
>>>Which version do you use, and which 'profiling' features did you use
>>>(function trace or real profiles)?
>>
>>1.3.1 stable as reported by the pear installer. I am trying to use
>>auto_profile_mode 2, but I am in no way glued to this option :) As it
>>turned out with my searches, there is no documentation for the
>>cachegrind output yet, or at least I was unable to find that.
>
> That's correct as I'm still writing that, and as you know Developers
> hate Documentation ;-) For the cachegrind stuff to use you will need
> Xdebug 2.0-dev from CVS. Have a look at
> http://www.derickrethans.nl/pres-xdebug-montreal2004/talk.html slide 24
> for the php.ini options. This generates a file in /tmp
> (cachegrind.*.out) which you can then visualize with KCacheGrind (a KDE
> application). Within some time we'll most likely have a tool for
> Windows/MacOSX/Non-KDE too.
That implicitly means that I will be unable to get any tool to visualize
some profiling output with xdebug 1.3.1?
Goba
Received on Sat Jun 05 2004 - 13:43:20 BST
This archive was generated by hypermail 2.2.0 : Mon Jun 25 2018 - 06:00:03 BST