|
From: Nicholas N. <nj...@cs...> - 2008-02-11 21:12:28
|
On Mon, 11 Feb 2008, Josef Weidendorfer wrote: > But to be true, the current solution looks quite "hacky" to me. To use it, > one has to modify things in the python interpreter, and there is this > special case for python in callgrind. Up to now, callgrind is independent > from the language used, as long as there exists debug information for the > binary. I agree. We also try to avoid conditional compilation, and dependencies on external software, including headers. But it is useful to mixed Python/C programmers, so it would be nice if there is a cleaner way to do it. N |