From: Daniel Jacobowitz <drow@false.org>
To: Michael Snyder <msnyder@redhat.com>
Cc: Jim Blandy <jimb@red-bean.com>,
GDB Patches <gdb-patches@sources.redhat.com>,
gdb@sources.redhat.com, Eli Zaretskii <eliz@gnu.org>
Subject: Re: [RFC] multi-process gdb (forks, checkpoints)
Date: Wed, 30 Nov 2005 13:10:00 -0000 [thread overview]
Message-ID: <20051130024701.GA8632@nevyn.them.org> (raw)
In-Reply-To: <438D0753.4050106@redhat.com>
On Tue, Nov 29, 2005 at 05:58:43PM -0800, Michael Snyder wrote:
> Jim Blandy wrote:
> >What happens if we fork, and then one of the forks unloads or loads a
> >shared library?
> >
> >We're really crippled by our symtab data structures.
>
> Hmmm... unload would be the bigger problem, I suppose.
Yes. Eventually we just need to improve the symtab interface enough to
permit this. I think it's not an unreachable goal. The user interface
is going to get thornier and thornier, though.
> I'd look at it this way -- this is really a subset of "debugging
> separate processes". The subset is, processes that share the same
> symbol set. What you suggest is crowding that boundary. ;-)
>
> We know that the set of programs that can be debugged this way
> is prescribed. Can't do multi-threaded programs, for instance.
Right - we can't duplicate them - we could more or less fake it, but
they know too much about their TIDs, and their TLS, et cetera.
--
Daniel Jacobowitz
CodeSourcery, LLC
prev parent reply other threads:[~2005-11-30 2:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-29 4:41 Michael Snyder
2005-11-29 19:20 ` Eli Zaretskii
2005-11-30 3:00 ` Michael Snyder
2005-11-30 5:41 ` Jim Blandy
2005-11-30 11:39 ` Michael Snyder
2005-11-30 13:10 ` Daniel Jacobowitz [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=20051130024701.GA8632@nevyn.them.org \
--to=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=gdb@sources.redhat.com \
--cc=jimb@red-bean.com \
--cc=msnyder@redhat.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