From: Daniel Jacobowitz <drow@false.org>
To: gdb@sourceware.org
Subject: Re: Multi process debugging using gdb - references?
Date: Mon, 26 Mar 2007 14:51:00 -0000 [thread overview]
Message-ID: <20070326145137.GA24276@caradoc.them.org> (raw)
In-Reply-To: <200703260739.13463.fnf@specifix.com>
On Mon, Mar 26, 2007 at 07:39:13AM -0700, Fred Fish wrote:
> My gut feeling says that using some front end to control multiple
> instances of gdb is probably a better solution than trying to enhance
> gdb to handle this using a single gdb process.
I have not done any work in the multi-process area in years, but
that's my gut feeling too. GDB's internals and user interface are
both very wound up in a single process model.
That's not to say it couldn't be changed. But you'd have to convince
us first that it was worth changing, and then that it was practical.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-03-26 14:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-26 14:39 Fred Fish
2007-03-26 14:51 ` Daniel Jacobowitz [this message]
2007-03-26 15:54 ` Gary Funck
[not found] ` <1174945438.24110.48.camel@localhost.localdomain>
2007-03-26 22:13 ` 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=20070326145137.GA24276@caradoc.them.org \
--to=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