[cmake-developers] dependency scanning speed

[Bill Hoffman]

At 05:58 AM 9/10/2006, Alexander Neundorf wrote:
>I tried callgrind, but it doesn't work.
>I have kubuntu, valgrind 3.0.1 and callgrind 0.10.1.
>It starts and finishes after approx 3 seconds (instead of 30). 10 percent of 
>the time are spent in cmake, 50 in ld and 30 percent in libc. So it seems 
>cmake quits immediately after starting.
>Any idea what's wrong ? 

Often times when the problem is due to disk access calgrind is not much help.
The overhead of calgrind makes it so the disk can keep up with the process.
The only way to debug, is it add timers in the code directly.  So, it sounds
like the problem is accessing all of those files.

-Bill