From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20272 invoked by alias); 14 May 2008 08:07:55 -0000 Received: (qmail 20262 invoked by uid 22791); 14 May 2008 08:07:54 -0000 X-Spam-Check-By: sourceware.org Received: from cantor.suse.de (HELO mx1.suse.de) (195.135.220.2) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 14 May 2008 08:07:31 +0000 Received: from Relay2.suse.de (mail2.suse.de [195.135.221.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.suse.de (Postfix) with ESMTP id 95332413A7; Wed, 14 May 2008 10:07:26 +0200 (CEST) From: Andreas Schwab To: David Miller Cc: drow@false.org, 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'" References: <20080513230220.GA28151@caradoc.them.org> <20080513.181050.211688658.davem@davemloft.net> <20080514024640.GA8332@caradoc.them.org> <20080513.212144.50306766.davem@davemloft.net> X-Yow: I will SHAVE and buy JELL-O and bring my MARRIAGE MANUAL!! Date: Wed, 14 May 2008 18:05:00 -0000 In-Reply-To: <20080513.212144.50306766.davem@davemloft.net> (David Miller's message of "Tue, 13 May 2008 21:21:44 -0700 (PDT)") Message-ID: User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit 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/msg00428.txt.bz2 David Miller writes: > 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. There is probably no symbol matching printf in the debugging information. That's how it looks like on ppc, where the two versions of printf are just aliases of the internal names __printf and __ndbl_printf. Andreas. -- Andreas Schwab, SuSE Labs, schwab@suse.de SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."