Re: profiling my own shared libraries

[Andreas Jaeger]

Peter Bienstman <address@hidden> writes:

> Hi,
>
> I'm able to profile system shared libraries with sprof, e.g.
>
> LD_PROFILE=glibc.so.6
> <run program>
> ls /var/tmp
> sprof ...
>
> However, for my own shared library (a Python extension module), no
> output is produced in /var/tmp

Is it loaded?  Did you specify the correct name?  Try LD_DEBUG=files
(or libs) in the environment (LD_DEBUG=help ls gives help).

> I did type the name of my library correctly, without any path. I noticed
> however that the name of my library does not start with 'lib' (it's a
> Python module), but I don't suppose this causes any problems?

Shouldn't cause a problem,

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