From: Tom Tromey <tromey@redhat.com>
To: Stan Shebs <stanshebs@earthlink.net>
Cc: Paul Koning <Paul_Koning@dell.com>,
andrew.stubbs@st.com, gdb@sourceware.org
Subject: Re: Symbol tables for separately linked pieces
Date: Mon, 14 Jul 2008 19:04:00 -0000 [thread overview]
Message-ID: <m3mykk70ei.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4876423A.8050603@earthlink.net> (Stan Shebs's message of "Thu\, 10 Jul 2008 10\:09\:14 -0700")
>>>>> "Stan" == Stan Shebs <stanshebs@earthlink.net> writes:
Daniel> Yes - once we're rolling on that project, expect discussion on this
Daniel> list :-)
Stan> I'm kind of creeping on it now, mostly looking at symbol table code to
Stan> get an idea of what to change. From the user point of view, it seems
Stan> pretty natural to extend the source-and-line concept to be
Stan> program-and-source-and-line with lots of defaulting, just as line
Stan> number alone has an implicit source file.
Stan> My chicken scratchings on paper tend to encourage the introduction of
Stan> a fully general many-to-many mapping between inferior processes and
Stan> objfiles, but I don't yet know if that is overly ambitious for this
Stan> round of hackery.
The earlier you can talk about your thoughts, and the more you can
say, the better. It is ok by me if it is internally inconsistent or
missing things or whatever -- we (Red Hat) are also looking into
various debugger things and this kind of information definitely helps.
Tom
next prev parent reply other threads:[~2008-07-14 19:04 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
2008-07-10 16:13 ` Daniel Jacobowitz
2008-07-10 17:10 ` Stan Shebs
2008-07-14 19:04 ` Tom Tromey [this message]
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=m3mykk70ei.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=Paul_Koning@dell.com \
--cc=andrew.stubbs@st.com \
--cc=gdb@sourceware.org \
--cc=stanshebs@earthlink.net \
/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