|
From: Josef W. <Jos...@gm...> - 2014-12-01 14:30:06
|
Am 01.12.2014 um 12:32 schrieb David Fernandez Lopez: > valgrind --dsymutil=yes --tool=callgrind --trace-children=yes > --separate-threads=yes --instr-atstart=no --collect-atstart=no > --collect-systime=yes <my_program> Remove "--collect-atstart=no" and "--instr-atstart=no". Does it work this way? Josef > > The results show a lot of functions with 0 CPU cycles, but these > functions are called a lot of times. > > For example: > > fn=(13976) aes_icm_encrypt > cfn=(13978) aes_icm_encrypt_ismacryp > calls=2883 0 > 0 0 1 13 > > But, the output gives correct information about functions in the same > library. Theses functions have a high overhead and they are the > bottleneck of my application. > > Do you have any clue why I don't have CPU cycles information about these > functions? > > Thanks in advance. > Regards. > > -- > David Fernández López > |