I am trying to put at work (for the first time) VTune Amplifier XE 2016 on a Linux C++ code.
I am facing with the following issue:
I have a class with methods ‘detectElements’ and ‘detectAxisElements’.
‘detectElements’ is calling ‘detectAxisElements’ twice with different parameters (there is no other call to ‘detectAxisElements’ in my code).
Looking at VTune’s result, I can see in the Caller/Callee tab:
For “CPU Time: Total”
For “CPU Time: Self”
‘detectAxisElements’ does not seem to be recognized as being called from ‘detectElements’.
Looking at the “Callees pane” for ‘detectElements’, I can see several other methods and operators but nothing about 'detectAxisElements’.
Any hint to let me understand this point is welcome.
And which compiler are you using? It could be that the method is being inlined by the compiler. Try setting the 'inline-debug-info' debug flag (Intel compiler supports this and I think gcc does as well).
If you don't include stacks, you can't use the "Caller/Callee" tab since there is no information about who called whom.
Also, you will notice in the Bottom Up display, if you attempt to expand the function call stack, the "No call stack info" message will be displayed. To see any calling sequences, you must select one of the configurations that includes "stacks." Then, you will only see calling sequences that were executed and had samples collected during their execution.
Last weeks, I tried to select the option "Hotspots, stacks and context switches", but I got the message that because of selected "context switches", sampling driver was required and not found. And I couldn't use the "Start" button. (I have no root access and I did not have the rights for the driver installation)
Today, I got the same warning message but I was able to start the analysis and I got the expected results (calls hierarchy correctly reported).
So the initial problem seems to be solved.
Just remains the mystery of the behavioural change...
Maybe you made some remote actions... ;=) Thanks a lot!