Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Paul Koning <Paul_Koning@dell.com>
To: drow@false.org
Cc: andrew.stubbs@st.com,     gdb@sourceware.org
Subject: Re: Symbol tables for separately linked pieces
Date: Thu, 10 Jul 2008 15:56:00 -0000	[thread overview]
Message-ID: <18550.12532.359181.233284@gargle.gargle.HOWL> (raw)
In-Reply-To: <20080710150728.GA12544@caradoc.them.org>

>>>>> "Daniel" == Daniel Jacobowitz <drow@false.org> writes:

 Daniel> On Thu, Jul 10, 2008 at 03:55:58PM +0100, Andrew STUBBS
 Daniel> wrote:
 >> 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").

 Daniel> I don't have a suggestion, but I do have a hopeful sign: the
 Daniel> same sort of juggling is necessary for a
 Daniel> multiple-process-image GDB, which CodeSourcery's going to be
 Daniel> working on once we're finished with non-stop debugging and
 Daniel> multi-process-single-image.  Whatever we come up with will
 Daniel> hopefully be useful for this two image scenario too.

 Daniel> I suspect we'll tell GDB to keep both symbol tables loaded,
 Daniel> but have one current.  But I haven't really thought about it
 Daniel> (I'm working on other things).

Interesting,

The hack implementation I have right now is in the context of a dump
analyzer.  I do the "load both and have one current" thing.  On top of
that, I also allow the analyzer to find the current process (or any
other process) and load its symbol tables (including shared libraries,
eek).  It's not a common thing but occasionally it's nice to trace a
kernel crash all the way down into userland.

Maybe we should compare notes.

      paul


  reply	other threads:[~2008-07-10 15:56 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
2008-07-10 15:07   ` Daniel Jacobowitz
2008-07-10 15:56     ` Paul Koning [this message]
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=18550.12532.359181.233284@gargle.gargle.HOWL \
    --to=paul_koning@dell.com \
    --cc=andrew.stubbs@st.com \
    --cc=drow@false.org \
    --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