From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: drow@false.org (Daniel Jacobowitz)
Cc: jjaimon@yahoo.com (Jaimon Jose), gdb@sourceware.org
Subject: Re: Setting breakpoints where duplicate symbols are present
Date: Sat, 05 May 2007 13:37:00 -0000 [thread overview]
Message-ID: <200705051337.l45Db8Jk008733@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <20070505044408.GA32240@caradoc.them.org> from "Daniel Jacobowitz" at May 05, 2007 12:44:08 AM
Daniel Jacobowitz wrote:
> On Sat, May 05, 2007 at 08:26:47AM +0530, Jaimon Jose wrote:
> > My questions are:
> > 1. How do I inspect all the symbols of the same name in the process
> > space? ( I tried loading the symbol from each library
> > load-symbol-file. It didn't help either. In case of ambiguity, dbx used
> > to show all symbols qualified with the library name and let us choose
> > the right one)
> > 2. How do I qualify a symbol with the library name where it belongs to?
> > ( for eg. `libfoo.so`foo_bar )
>
> Basically, you can't. Yet. We know we need to fix this.
B.t.w., Markus is currently working on a patch:
http://sourceware.org/ml/gdb-patches/2007-05/msg00037.html
that will at least have GDB follow the ld.so symbol lookup rule,
so if you access a symbol name from within a frame belonging
to a -Bsymbolic shared library, you'll get the symbol definition
from within that library.
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
prev parent reply other threads:[~2007-05-05 13:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-05 2:57 Jaimon Jose
2007-05-05 4:44 ` Daniel Jacobowitz
2007-05-05 13:37 ` Ulrich Weigand [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=200705051337.l45Db8Jk008733@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=drow@false.org \
--cc=gdb@sourceware.org \
--cc=jjaimon@yahoo.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