Re: [RFC] Fix for mishandling of "break 'pthread_create@GLIBC_2.2.5'"

[David Miller <davem@davemloft.net>]

From: Daniel Jacobowitz <drow@false.org>
Date: Tue, 13 May 2008 22:46:40 -0400

> On Tue, May 13, 2008 at 06:10:50PM -0700, David Miller wrote:
> > > What's different for SPARC in this regard from other targets?  Is it
> > > lack of a PLT entry (or BFD synthetic symbol for said PLT entry)?
> > 
> > There is a PLT entry, and when I disassemble it it looks like
> > "printf@plt".
> > 
> > But when I set a breakpoint it gets set on printf@GLIBC_2.0
> > instead of the correct printf@@GLIBC_2.4
> > 
> > All of my other systems have one non-versioned printf symbol,
> > so either that is the different or the ordering of the symbols.
> 
> Yes, this is probably an impact of the 128-bit long double transition.
> GDB knows how to set multiple breakpoints on functions with debug
> info, but not without debug info (a known issue).

My case has full debugging information, or at least it should, via
/usr/lib/debug/lib/ultra3/libc-2.6.1.so which is where I got those
above symbols above from.