[Kcachegrind-callgrind] Re: kcachegrind reporting .so files to be without debug info

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

On Thursday 15 September 2005 08:42, you wrote:
> [Emailing directly to you since the sourceforge mailing list looks
>  like it doesn't get much use]

That probably would be the perfect discussion to start using the mailing 
list...

> That is: it finds the source for the main() function, and it finds the
> source for all inline code, but it can't find the source for any of
> the code in the .so files.  It says eg.:
>
>  There is no source available for the following function:
>    '0x3C6BBBC4'
>  This is because no debug information is present.
>  Recompile source and redo the profile run.
>  The function is located in this ELF object:
>    'libsomename.so.1.0'
>
> However I know I compiled that .so (as well as everything else) with
> debug info.  And I'm able to run the program in gdb and set
> breakpoints in functions in that library, and look at variables when I
> stop there.

This should be a problem in Valgrinds debug reader then. If you run memcheck, 
are there any errors so that you can verify that this problem is in fact 
Valgrinds?

> Is there some option I should have run callgrind with?

No.

> Is there some 
> g++ demangling difference between 3.3 and 4.0 (the kcachegrind I'm
> using is linked against libstdc++.so.5 so I guess that means it's
> compiled with gcc 3.3 as well.  Don't know if that means anything?).

KCachegrind does not do any demangling. This is done by VG, and the profile 
data contain the demangled names.

Besides, this only would be the problem if you get mangled symbols. But you 
get no debug info as all, as far as I see.

Josef

>
> Thanx!
>
>
> - Steinar