I am trying to see where my code spends time on many instructions (doesn't have to be time, just number of instructions).
I see many recommendations for callgrind, which I did start using, but I don't see much I can do more than callgrind_control -b -e, which just shows a current stack trace.
Is there a way to find a line in my code that uses many insturctions overall, and called many times? I prefer it to be my code, rather than, for example, the STL library, which I do call a lot -- so I want to abstract away from that, and see exactly which line of my code spends many instructions, including calls to STL.