Added: Ability to click on functions listed in 'calls' and 'called from' info slides to fill details of said function ( issue 29 )
Fixed: Changed default setting of $storageDir to empty string. This allows webgrind to use system defaults or user may override.
WFM I had to change a line in config.php to read thus:
static $xdebugOutputFormat = '/^trace\.[0-9]+\.xt/';
After this webgrind could find the trace files.
When I tried to analyze the files it created two httpd process that took 70% of CPU each. The trace file then mushroomed to 1.6GB.
I am using latest MAMP, with all the zend accelerator features turned off. (Version 0.71.2)
JACOB OETTINGER That does not sound good. The generated preprocessed file should be smaller than the original xdebug profile file.
It would be great if you could supply me with the xdebug trace that, when parsed, generated that enormous file.
jacob@oettinger.dk (bring on the spam :) (Version 0.71.2)
JACOB OETTINGER Turns out your problem was caused by a bug introduced in 0.7. The problem has been fixed in 0.81.
Thank you for reporting the problem. (Version 0.71.2)
