From: David Miller <davem@davemloft.net>
To: ppluzhnikov@google.com
Cc: 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:26:00 -0000 [thread overview]
Message-ID: <20080513.151626.265832990.davem@davemloft.net> (raw)
In-Reply-To: <8ac60eac0805131351s241d33a8pd7d9839c51e53a8d@mail.gmail.com>
From: "Paul Pluzhnikov" <ppluzhnikov@google.com>
Date: Tue, 13 May 2008 13:51:57 -0700
> On Tue, May 13, 2008 at 1:23 PM, Michael Snyder <msnyder@specifix.com> wrote:
> >
> > FYI, there's a sort-of work-around...
>
> That only sort-of-works because there is a matching non-versioned
> symbol. In addition, it's quite annoying for TAB-completion to
> complete the symbol, but the result of completion to then not work.
Right.
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 :-)
next prev parent reply other threads:[~2008-05-13 22:16 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 [this message]
2008-05-14 4:30 ` Daniel Jacobowitz
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=20080513.151626.265832990.davem@davemloft.net \
--to=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