How do you profile an executable that loads shared libraries?

[Tristan Gingold]

On Feb 23, 2009, at 3:59 PM, Mike Frysinger wrote:
> the kernel provides one virtually contiguous address range to each  
> userspace
> program and each application/shared object gets a dedicated chunk of  
> that.  so
> unless it's a matter of the profiling code not saving the address  
> map so the
> addresses can be coordinated after the fact, i dont see how this  
> would be an
> issue.

With shared libraries, the address map is sparse.  The gprof  
technology was not designed for
a sparse address map and does not deal with libraries.
We can of course use it with shared libraries but they won't be  
profiled.