Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Avi Gozlan <avi@checkpoint.com>
Cc: "'gdb\@sourceware.org'" <gdb@sourceware.org>
Subject: Re: Differentiating symbols in multiple copies of shared libraries
Date: Thu, 09 Dec 2010 21:53:00 -0000	[thread overview]
Message-ID: <m3k4ji1ulx.fsf@fleche.redhat.com> (raw)
In-Reply-To: <9C4E85B61203CD419BB3A638E5F6833301A37EBFB20B@il-ex01.ad.checkpoint.com>	(Avi Gozlan's message of "Thu, 9 Dec 2010 17:50:30 +0200")

>>>>> "Avi" == Avi Gozlan <avi@checkpoint.com> writes:

Avi> We did not find a way for GDB to refer to a symbol in a specific
Avi> copy of the object file (other then referring to the specific
Avi> address).

There is currently no way to do this.

Avi> Please note that we need to differentiate between symbols not only
Avi> for defining breakpoints but for other needs such as disassembly,
Avi> backtrace as well.

Avi> Your input regarding this issue will be appreciated.

I think it would be a welcome addition to gdb.

The dbx syntax doesn't seem particular gdb-ish to me, but it would do.
HPD-like syntax along the lines of "#libfoo.so#function" has also been
suggested.

If you implement this in linespecs, which is the natural approach, then
it will automatically work for disassembly.

For "backtrace", I guess you mean that at least ambiguous symbols should
be printed in this syntax in a backtrace.  I'm sure that is doable as
well.

I am not sure whether anybody is working on this.  At the very least,
please file a bug.

Tom


  reply	other threads:[~2010-12-09 21:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-09 15:50 Avi Gozlan
2010-12-09 21:53 ` Tom Tromey [this message]
2011-01-23 12:07   ` Avi Gozlan
2011-01-27 20:52     ` Tom Tromey

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=m3k4ji1ulx.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=avi@checkpoint.com \
    --cc=gdb@sourceware.org \
    /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