Re: [Valgrind-users] Problems with callgrind_annotate

[<aul...@mi...>]

Nick,

Thank you for the fast reply!  I commented out the dlclose, rebuilt, and
callgrind works much better.  It is still complaining about the
"Possible precedence problem" but it seems to have done the real work
anyway.

Now I just hope I can remember this for the next time I use callgrind.
At least it will be in the list archives now for me to find.  :D

Thanks again,
Ashley

-----Original Message-----
From: Nicholas Nethercote [mailto:nj...@cs...]=20
Sent: Wednesday, May 23, 2007 8:29 PM
To: aulwelling
Cc: val...@li...
Subject: Re: [Valgrind-users] Problems with callgrind_annotate

On Wed, 23 May 2007 aul...@mi... wrote:

> I have run into an problem with callgrind that cachegrind does not=20
> seem to have.  I have some code which is compiled (using gcc on Linux)

> into a shared library.  An application dlopens this library and makes=20
> various calls into it.  For some reason callgrind can't/won't annotate

> the files I'm interested in this library, but cachegrind has no
trouble with them.

Josef might be able to give more info, but the basic problem is caused
by the dlopen'd library subsequently being dlclosed.  Cachegrind handles
this, but Callgrind does not -- all the information for the instructions
in the library get merged into a single "???" entry.  (Cachegrind used
to do the same thing, and then I worked out a fix, but I think there was
some reason why that fix wasn't appropriate for Callgrind.)

A hacky possible workaround:  can you avoid dlclosing the library?

Nick