Open GoogleCodeExporter opened 8 years ago
[deleted comment]
Have you verified that you can see actual cachegrind files being generated in
your profiler_output_dir location? If you do see files there, then it sounds
like webgrind just doesn't see them.
I found today that having the %s script name piece in the profiler_output_name
file format mask would result in webgrind not seeing any of the cachegrind
files that I verified were in my profiler_output_dir.
You might try commenting out the profiler_output_name, thereby letting it
default to cachegrind.out.%p , generate some cachegrind files that are in that
format, and see if webgrind can see those.
Original comment by demon.g...@gmail.com
on 3 Sep 2010 at 8:54
Duplicate of issue #36?
Original comment by demon.g...@gmail.com
on 3 Sep 2010 at 8:59
Might be obvious, but did you verify that you have the xdebug module installed?
That one got me :)
Original comment by joehhard...@gmail.com
on 10 Jan 2013 at 1:46
Same issue here. I used the same link:
http://anantgarg.com/2009/03/10/php-xdebug-webgrind-installation/
to install xdebug and webgrind. It does not find any cachegrind files and when http://localhost/webgrind is opended shows this-->
Select a cachegrind file above
(looking in C:\xampp\htdocs\webgrind\tmp/ for files matching
/^cachegrind.out..+..+$/)
My environment:
Windows vista
xampp 1.7.7
php 5.3.8
Original comment by gtsde...@hotmail.com
on 19 Apr 2013 at 12:27
Original issue reported on code.google.com by
webelco...@gmail.com
on 31 May 2010 at 8:23