This is probably due to aggressive compiler optimizations.The compiler can do all sorts of things, such as inlining, moving code around to optimize for locality, etc. It's not a debug info issue.
When you aggressively optimize with the compiler, you probably need to view the performance data at a higher level, such as the Hotspot view, since the mapping of source to instructions becomes very difficult.
Displaying data for inlined functions is problematic and something the VTune analyzer team has been grappling with. At this point in time, there are cases where the display of the sampling data for an inlined instance of a function is not optimal. The best thing to do, if you know it is an inlined function, is to switch to the assembly view and look at the actual instructions. This will always be correct.
Debug info for inlined functions is evolving and future releases of the VTune analyzer may present the data more effectively.
However, I don't believe this is related to the problem that pdonahue is seeing.
Message Edited by DaveA on 04-11-2006 10:57 AM