Re: [Valgrind-users] profiling/debugging inside shared objects

[Josef W. <Jos...@gm...>]

On Monday 07 April 2003 14:40, Nicholas Nethercote wrote:
> On Fri, 4 Apr 2003, Charlls Quarra wrote:
> >  I wonder if there are issues about profiling
> > dinamically loaded plugins? valgrind --skin=cachegrind
> > doesnt seem to produce any relevant info about code in
> > those plugins, only code in statically linked
> > libraries
>
> Hmm, in theory there should be no problems, Valgrind (and hence
> Cachegrind) can handle dlopen'd plugins ok...

But they are unmapped before program termination. You only get one cost line 
"discarded" for all plugins. The solution would be to allow dumping while the 
plugin is mapped. Or you dump the information of BBCCs when the according 
object is unmapped.

Or you don't delete BBCCs and accumate cost to "discarded", but keep them.
Now you have the problem that a BB start address isn't unique to get to the 
right BBCC, but you have to store the SegInfo* in the BBCCs to distinguish 
among BBs from different plugins at the same address.

BTW, my Calltree skin should be buggy in this regard, as it doesn't delete any 
BBCCs on unmapping, but still only uses the BB address. But checking the 
SegInfo* should be easy enough for a fix.
Perhaps it's even better to take BBCCs of unmapped objects from the hash into 
a list, and put them in again if the object is mapped again after adjusting 
the addresses if needed. The same object could be mapped on a different base 
address.

Josef


>
> N
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: ValueWeb:
> Dedicated Hosting for just $79/mo with 500 GB of bandwidth!
> No other company gives more support or power for your dedicated server
> http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/
> _______________________________________________
> Valgrind-users mailing list
> Val...@li...
> https://lists.sourceforge.net/lists/listinfo/valgrind-users