[Valgrind-developers] Re: Address lookups and kcachegrind

[Carlo W. <ca...@al...>]

On Fri, Nov 15, 2002 at 09:02:35PM +0100, Josef Weidendorfer wrote:
> By mistake, loading of weak symbols was commented out in valgrinds symbol 
> loader (BAD BUG !!).
> I checked out libecc and did a testrun. 
> In fact, I have not a single "0x..." or "???" here at all.

Hmm, I did (for a library without any debugging symbols?)

kcachegrind gave me:

	0x404ACCA4		libcwd.so.99.26:stl_map.h

This is nonsense: stl_map.h is not a header file of libcwd
and 0x404ACCA4 has no debugging symbols, so it can't
(known to) be in to stl_map.h (actually, I can't figure
out to which library it belows to at all: without cachegrind
running, there is no library loaded at all at that address;
and neither is there while cachegrind is running).  I tried
also to put a break point at that address with gdb, but it
never comes there.  Weird that it shows up in the output of
cachegrind.

-- 
Carlo Wood <ca...@al...>