From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32445 invoked by alias); 14 May 2008 04:22:09 -0000 Received: (qmail 32433 invoked by uid 22791); 14 May 2008 04:22:08 -0000 X-Spam-Check-By: sourceware.org Received: from 74-93-104-97-Washington.hfc.comcastbusiness.net (HELO sunset.davemloft.net) (74.93.104.97) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 14 May 2008 04:21:51 +0000 Received: from localhost (localhost [127.0.0.1]) by sunset.davemloft.net (Postfix) with ESMTP id 8EBEAC8C1F2; Tue, 13 May 2008 21:21:44 -0700 (PDT) Date: Wed, 14 May 2008 17:33:00 -0000 Message-Id: <20080513.212144.50306766.davem@davemloft.net> To: drow@false.org Cc: ppluzhnikov@google.com, gdb-patches@sourceware.org, dje@google.com, msnyder@specifix.com Subject: Re: [RFC] Fix for mishandling of "break 'pthread_create@GLIBC_2.2.5'" From: David Miller In-Reply-To: <20080514024640.GA8332@caradoc.them.org> References: <20080513230220.GA28151@caradoc.them.org> <20080513.181050.211688658.davem@davemloft.net> <20080514024640.GA8332@caradoc.them.org> X-Mailer: Mew version 5.2 on Emacs 22.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2008-05/txt/msg00425.txt.bz2 From: Daniel Jacobowitz 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.