From: Avi Gozlan <avi@checkpoint.com>
To: "'gdb@sourceware.org'" <gdb@sourceware.org>
Cc: Avi Gozlan <avi@checkpoint.com>
Subject: Differentiating symbols in multiple copies of shared libraries
Date: Thu, 09 Dec 2010 15:50:00 -0000 [thread overview]
Message-ID: <9C4E85B61203CD419BB3A638E5F6833301A37EBFB20B@il-ex01.ad.checkpoint.com> (raw)
Hello,
In an implementation of a multi-threaded program we need to have multiple instances of the same text residing in different virtual addresses. For this purpose different copies of the object file are loaded using dlopen().
We did not find a way for GDB to refer to a symbol in a specific copy of the object file (other then referring to the specific address). I know that DBX supports this by qualifying `<shared object name>`<function name>. Is there similar feature in GDB?
Quoting Daniel J. from a message posted in May 2007 it seemed that this issue was already known:
"> 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."
Is this fixed?
Please note that we need to differentiate between symbols not only for defining breakpoints but for other needs such as disassembly, backtrace as well.
Your input regarding this issue will be appreciated.
Avi
next reply other threads:[~2010-12-09 15:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-09 15:50 Avi Gozlan [this message]
2010-12-09 21:53 ` Tom Tromey
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=9C4E85B61203CD419BB3A638E5F6833301A37EBFB20B@il-ex01.ad.checkpoint.com \
--to=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