Infinite loop/file identification with prepend

[staab]

Remember that old infinite loop problem that happened when webgrind profiled the file that was currently being generated by xdebug on the profiler (http://code.google.com/p/webgrind/issues/detail?id=12)? Well, it persists (sorta).

If you run a prepend on the php files in your project, but fail to make an exception for Webgrind, Webgrind fails to recognize its own files, and ends up listing them in the drop-down as well as potentially trying to profile them. The reason for this is Webgrind identifies the file name as the name of the prepend file, rather than the actual target file. Basically, the target file acts like it is included in the prepend file, so all processed files come back as prepend.php.

This problem is technically our fault for running a prepend, but I thought it would be good information to have, in case anyone ever had the same problem, or you wanted to find a fix.

Thanks for the awesome profiling tool!