Re: how to profile my own shared libs loaded with dlopen?

[Andreas Jaeger]

Harald Kirsch <address@hidden> writes:

> With the help of deja (google) I found out that sprof might do the
> trick. Since rpm showed that sprof belongs to the glibc-package, I
> dare to ask this here.
> 
> If I set LD_PROFILE to libc.so.6 (on Linux), I get a .profile, but
> there is no .profile if I set LD_PROFILE to the name of my shared lib,
> which is loaded by the python interpreter presumably with dlopen.
> 
> I wonder if the mechanism works at all for anything but libc?

It should work.  Did you really use the correct name (soname) of the
lib?

Andreas
-- 
 Andreas Jaeger
  SuSE Labs address@hidden
   private address@hidden
    http://www.suse.de/~aj