symbol versioning...

David Miller davem@davemloft.net
Sat Nov 26 21:25:00 GMT 2011


From: Jan Kratochvil <jan.kratochvil@redhat.com>
Date: Sat, 26 Nov 2011 22:11:00 +0100

> On Sat, 26 Nov 2011 21:56:33 +0100, David Miller wrote:
>> These all fail on my sparc systems because my libc.so has two printf
>> symbols, each with a different ELF version.  The older version appears
>> first in the dynamic symbol table, so that's the one which GDB uses, and
>> it's therefore not the one the executable will actually call.
> 
> I should sometimes commit this patch:
> 	Re: [patch] Fix C++ demangling of minsyms with symver
> 	http://sourceware.org/ml/gdb-patches/2011-06/msg00045.html
> 
> Maybe implementing its part:
> # One can see the default resolving to the @@ variant is not implemented.  Not
> # sure if it should be but let that be a possible incremental patch in the
> # future.
> 
> would solve this problem?

Thanks a lot for the reference, I'll take a look!

>> I can think of two ways to handle this:
> 
> (3) With Tom Tromey's pending linespec patch GDB maybe could put a breakpoint
>     on all the versions of such symbol.

Even better :-)



More information about the Gdb mailing list