From: Christoph B. <bar...@or...> - 2006-09-13 08:19:41
|
Hi, with the recent fixes I am able to profile the part of the code that is interessting for me. But there is one problem left. Sometimes after starting instrumentation it switches itself off again. And I have to restart it. Given this I cannot be sure that instrumentation is always done and that I do not forget to switch it on again. Here is a log of a sample session: -bash-3.00$ callgrind_control -i on 19970 PID 19970: program [requesting '+Instrumentation'...] OK. -bash-3.00$ callgrind_control -s 19970 PID 19970: program [requesting 'Status'...] Number of threads: 1 Events collected: Ir Dr Dw I1mr D1mr D1mw I2mr D2mr D2mw Functions: 1,636 (executed 257,435, contexts 1,636) Basic blocks: 3,894 (executed 4,762,919, call sites 2,233) -bash-3.00$ callgrind_control -s 19970 PID 19970: program [requesting 'Status'...] No information available as instrumentation is switched off. -bash-3.00$ callgrind_control -i on 19970 PID 19970: program [requesting '+Instrumentation'...] OK. -bash-3.00$ callgrind_control -s 19970 PID 19970: program [requesting 'Status'...] Number of threads: 0 Events collected: Ir Dr Dw I1mr D1mr D1mw I2mr D2mr D2mw Functions: 563 (executed 141,123, contexts 563) Basic blocks: 3,464 (executed 983,886, call sites 2,050) -bash-3.00$ callgrind_control -s 19970 PID 19970: program [requesting 'Status'...] Number of threads: 0 Events collected: Ir Dr Dw I1mr D1mr D1mw I2mr D2mr D2mw Functions: 1,181 (executed 2,334,797, contexts 1,181) Basic blocks: 8,057 (executed 16,365,930, call sites 4,962) Christoph |