Right now, as part of its profiling capabilities, Xdebug (http://xdebug.org) dumps profiling information into files that use KCacheGrind’s format. When this functionality was added to Xdebug there was not yet a formal specification (http://kcachegrind.sourceforge.net/html/CallgrindFormat.html) of this format, and thus the reverse-engineered implementation has subsequently acquired some issues. Since version 0.6, KCacheGrind is a bit more strict about the interpretation of the file format, which now causes an issues with Xdebug: https://bugs.kde.org/show_bug.cgi?id=256425
The donations belonging to this plegde will allow me to correctly address the issue to restore the Xdebug/KCacheGrind integration into its former glory. Correctly addressing it, means in this case redoing much of how the profiler writes profiling files, and it’s not simply just a bugfix to add the missing line.
This campaign has ended, no more pledges can be accepted.
Comments (0)
You must be signed in to make a comment.