public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: jan.kratochvil@redhat.com
Cc: gdb@sourceware.org
Subject: Re: symbol versioning...
Date: Sat, 26 Nov 2011 21:25:00 -0000	[thread overview]
Message-ID: <20111126.162444.1128646032611845044.davem@davemloft.net> (raw)
In-Reply-To: <20111126211100.GA18383@host1.jankratochvil.net>

From: Jan Kratochvil <jan.kratochvil@redhat.com>
Date: Sat, 26 Nov 2011 22:11:00 +0100

> On Sat, 26 Nov 2011 21:56:33 +0100, David Miller wrote:
>> These all fail on my sparc systems because my libc.so has two printf
>> symbols, each with a different ELF version.  The older version appears
>> first in the dynamic symbol table, so that's the one which GDB uses, and
>> it's therefore not the one the executable will actually call.
> 
> I should sometimes commit this patch:
> 	Re: [patch] Fix C++ demangling of minsyms with symver
> 	http://sourceware.org/ml/gdb-patches/2011-06/msg00045.html
> 
> Maybe implementing its part:
> # One can see the default resolving to the @@ variant is not implemented.  Not
> # sure if it should be but let that be a possible incremental patch in the
> # future.
> 
> would solve this problem?

Thanks a lot for the reference, I'll take a look!

>> I can think of two ways to handle this:
> 
> (3) With Tom Tromey's pending linespec patch GDB maybe could put a breakpoint
>     on all the versions of such symbol.

Even better :-)

      reply	other threads:[~2011-11-26 21:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-26 20:56 David Miller
2011-11-26 21:11 ` Jan Kratochvil
2011-11-26 21:25   ` David Miller [this message]

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=20111126.162444.1128646032611845044.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=gdb@sourceware.org \
    --cc=jan.kratochvil@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).