Re: [Valgrind-users] valgrind not printing symbol names despite debug information included

[Bart V. A. <bar...@gm...>]

On Mon, Jul 7, 2008 at 4:03 PM, M B <sup...@go...> wrote:
> I crosscompiled a c++ application for ppc with g++-3.2 and glibc-2.3.2
> and linked it statically (I know linking statically against glibc is
> bad).
> Valgrind prints some errors, but doesn't print any symbol names,
> despite debug information.
> Valgrind 3.3.1 was natively compiled and linked against glibc-2.3.6.
> The native c++ compilers (3.3.6; 4.1.2, glibc-2.3.6) and another
> cross-compiler g++-4.0.0 with uclibc work, but I have to use g++-3.2
> for my application.
>
> I was able to reproduce this problem with any simple c++ application,
> but not wit a C application.
>
> Any ideas why Valgrind (memcheck) doesn't print symbol names? I build
> the crosscompiler (3.2) with crosstool, so I can change some options
> if I did something wrong.

The format of debug information differs between platforms and between
gcc versions. Valgrind can only print symbol names if it has been able
to parse the symbol information generated by the compiler. You can
verify whether Valgrind has been able to read symbol information by
passing the option --trace-symtab=yes to Valgrind.

Bart.