Right, one needs to remember that profile disassembly shows the contents of
the memory at the point you ask for the disassembly, where as the profile
data for those memory addresses is from the code executed from them,
*and that code can change*.
Ok that's fair. However it's even more difficult to understand what's going on with the timings under those circumstances :) it may be better to pick some example code to verify which is known to claim permanent residence at a given address... (I think we're still verifying, after all - it would be up to a user to decide how to interpret the figures for any given program, with code that moves around - and possibly stop it moving for performance measurement purposes!)
It seems that the DSP cycles diff column can be used to detect
code areas that have been modified (either self modifying
code or cross-processor modifications :))...
Yes it looks that way. A developer will generally know that a routine has been moved since it's a very deliberate process. However for a reverse engineering exercise, this knowledge will be absent so the trick becomes quite useful :-)
D.