|
From: Nicholas N. <nj...@cs...> - 2008-02-13 22:56:28
|
On Wed, 13 Feb 2008, Josef Weidendorfer wrote: >> A patch in contrib/ would be fine for the moment. But I am sure that a >> generic way to push higher level functions would interest a lot of >> people (so that there could be some callgrind plug-ins to profile >> python2.5, python2.3, php, perl, whatever...). > > Yes. > > However, there currently does not exist any further extension of VG > tools to allow for "callgrind plug-ins". But it should be possible to > make a kind of library version of callgrind, to base other VG tools > on it. > > Or even better: Support it via just an configuration file (or command line > options). Now that Julian is adding support for reading debug info for data, > it should be possible to look up arbitrary variables. I'd strongly encourage you to find a way, if possible, to make this feature generic if you plan to include it. Code that is not normally run (eg. due to being in contrib/, or only included if certain configure options are used) will be tested less and be much less robust. This is one of those things that is really important in practice. If the feature can be extended to other languages than Python that obviously makes it much better too. Nick |