search

daniloalvessouza / webgrind

Automatically exported from code.google.com/p/webgrind
Other
0 stars 0 forks source link

Provide workaround for Xdebug issue 357 #48

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
There is an obscure bug in Xdebug that has not been fixed yet. It results
in weird costs written to the cachegrind file.

http://bugs.xdebug.org/view.php?id=357

Here is a part of the cachegrind output file:

fl=php:internal
fn=php::function_exists
330 3

fl=php:internal
fn=php::function_exists
334 2

fl=php:internal
fn=php::function_exists
330 2

fl=php:internal
fn=php::function_exists
334 4293967300

fl=php:internal
fn=php::function_exists
330 1

fl=php:internal
fn=php::function_exists
334 3

fl=php:internal
fn=php::function_exists
330 1

fl=php:internal
fn=php::func

This confuses Webgrind total cost calculation, so that not all functions
are displayed in the profile.

I know that Webgrind is not to blame for Xdebug bugs, but apparently this
bug is hard to track down, so I suggest you provide a workaround until it
has been fixed.

This patch fixes the problem.

Original issue reported on code.google.com by c960657 on 15 Mar 2010 at 2:43

Attachments: