#1 Graphs shows calls that are not called

open
nobody
None
5
2007-01-23
2007-01-23
Anonymous
No

My test program calls a function EtnModuleImpl::checkVersion several times. Inside this function, a call to EtnActiveFilter::readNewConfig is made exactly the first time when EtnModuleImpl::checkVersion is called.

I'm interested in the call graph in a situation where EtnActiveFilter::readNewConfig is not called. I know that I have a test function PfEtnIssueEntryAppl::doTestLevel0_1 where this is the case (I instrumented the code with cout-calls for that purpose).

Nevertheless, whenn looking at the call graph for PfEtnIssueEntryAppl::doTestLevel0_1, I see the call to EtnModuleImpl::checkVersion (which is correct), but inside that also the call to EtnActiveFilter::readNewConfig (which is definitely incorrect).

Is that a correct visualization of kcachegrind? Can I rely on the performance numbers that kcachegrind shows?

I attach the described callgraph.

Any help would be appreciated!

Discussion

  • Call graph for problem

     
    Attachments