From: Andrew STUBBS <andrew.stubbs@st.com>
To: Paul Koning <Paul_Koning@dell.com>
Cc: gdb@sourceware.org
Subject: Re: Symbol tables for separately linked pieces
Date: Thu, 10 Jul 2008 14:58:00 -0000 [thread overview]
Message-ID: <487622FE.8050209@st.com> (raw)
In-Reply-To: <18550.7195.371436.629820@gargle.gargle.HOWL>
Paul Koning wrote:
> 1. When debugging in the subsystem, have its symbol table loaded "on
> top" -- so any name lookups are resolved first from that symbol
> table and only after that from the other (main program) table.
> 2. When I switch to debugging in the main program, I want to be able
> to tell GDB to deactivate the subsystem symbol table temporarily
> (or perhaps better yet, keep it around "on the bottom") so a
> name that exists in both is now resolved from the main program.
It's easy enough to switch between two sets of symbols using the
symbol-file command:
(gdb) symbol-file a.elf
....
(gdb) symbol-file b.elf
....
The symbol-file command throws away all previous symbols (including
those from add-symbol-file), and loads new ones. This way there never
are any duplicate symbols to get in the way.
This solution is less satisfactory when the context change occurs
frequently, so I've been wondering if there would be a better way to do
it myself. Some sort of context sensitive thing maybe (select symbols
from the same source as the current function symbol), or perhaps
explicitly by name ("break a.elf:main").
Andrew
next prev parent reply other threads:[~2008-07-10 14:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-10 14:27 Paul Koning
2008-07-10 14:58 ` Andrew STUBBS [this message]
2008-07-10 15:07 ` Daniel Jacobowitz
2008-07-10 15:56 ` Paul Koning
2008-07-10 16:13 ` Daniel Jacobowitz
2008-07-10 17:10 ` Stan Shebs
2008-07-14 19:04 ` Tom Tromey
2008-07-12 2:35 ` Michael Snyder
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=487622FE.8050209@st.com \
--to=andrew.stubbs@st.com \
--cc=Paul_Koning@dell.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