From: Daniel Jacobowitz <drow@false.org>
To: David Miller <davem@davemloft.net>
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'"
Date: Wed, 14 May 2008 04:30:00 -0000 [thread overview]
Message-ID: <20080513230220.GA28151@caradoc.them.org> (raw)
In-Reply-To: <20080513.151626.265832990.davem@davemloft.net>
On Tue, May 13, 2008 at 03:16:26PM -0700, David Miller wrote:
> I have a related problem right now in that the annota1 and annota3
> testcases fail on my machine because all of the printf symbols in
> libc are versioned and the one you get with a simple "b printf" is
> random and determined by the order in which the symbols get added to
> the minsym hashes:
>
> 0005b260 T printf@@GLIBC_2.4
> 001425c0 T printf@GLIBC_2.0
>
> GDB's support for symbol versioning could definitely be improved :-)
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)?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-05-13 23:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-13 19:11 Paul Pluzhnikov
2008-05-13 19:21 ` Daniel Jacobowitz
2008-05-13 22:16 ` Michael Snyder
2008-05-13 23:02 ` Paul Pluzhnikov
2008-05-13 23:16 ` Daniel Jacobowitz
2008-05-14 1:05 ` Paul Pluzhnikov
2008-05-14 8:16 ` Paul Pluzhnikov
2008-06-05 19:14 ` Daniel Jacobowitz
2008-06-06 2:14 ` Paul Pluzhnikov
2008-06-06 2:35 ` Daniel Jacobowitz
2008-05-14 4:26 ` David Miller
2008-05-14 4:30 ` Daniel Jacobowitz [this message]
2008-05-14 11:51 ` David Miller
2008-05-14 14:48 ` Daniel Jacobowitz
2008-05-14 17:33 ` David Miller
2008-05-14 18:05 ` Andreas Schwab
2008-05-14 18:09 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080513230220.GA28151@caradoc.them.org \
--to=drow@false.org \
--cc=davem@davemloft.net \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@specifix.com \
--cc=ppluzhnikov@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox