From: Russell Shaw <rjshaw@netspace.net.au>
Cc: gdb@sourceware.org
Subject: Re: Towards multiprocess GDB
Date: Mon, 21 Jul 2008 16:08:00 -0000 [thread overview]
Message-ID: <488405CE.3030901@netspace.net.au> (raw)
In-Reply-To: <1216600447.3549.486.camel@localhost.localdomain>
Michael Snyder wrote:
> On Fri, 2008-07-18 at 23:41 +0200, Mark Kettenis wrote:
>>> Date: Fri, 18 Jul 2008 13:40:08 -0700
>>> From: Stan Shebs <stanshebs@earthlink.net>
>>>
>>> CodeSourcery has a project to add "multiprocess" capability to GDB,
>>> and with this message I'd like to kick off some discussion of what
>>> that means and how to make it happen.
>> Please remind me, why was this a desirable capability again?
>
> Not answering for Stan, but from my experience, because
> people are asking for it. Parallel programs eventually
> go beyond threads.
>
> For instance I've had inquiries from several router mfgrs,
> who want to be able to debug their more advanced router systems
> that are running full-scale OS's (such as linux, bsd, and qnx)
> on the remote side. Also from makers of set top boxes of one
> sort or another, and multi-core cpu mfgrs (though there we get
> into multiple cores as well as multiple processes).
>
> But yes, I'd be interested in hearing what kinds of use cases
> CodeSourcery's customers are asking about as well...
Trying to contain all the dynamics of multiple processes in one gdb
doesn't suit the user interface of gdb well. Things would get pokey
and cluttered for the user.
One way would be to make multiple instances of gdb coordinate
via an IPC protocol.
next prev parent reply other threads:[~2008-07-21 3:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-18 20:50 Stan Shebs
2008-07-18 21:21 ` Paul Koning
2008-07-18 21:41 ` Stan Shebs
2008-07-21 0:34 ` Michael Snyder
2008-07-18 22:13 ` Mark Kettenis
2008-07-18 22:20 ` David Daney
2008-07-18 22:28 ` Thiago Jung Bauermann
2008-07-18 23:09 ` Stan Shebs
2008-07-19 3:53 ` Pedro Alves
2008-07-21 17:39 ` Stan Shebs
2008-07-21 1:53 ` Michael Snyder
2008-07-21 16:08 ` Russell Shaw [this message]
2008-07-21 17:57 ` Joel Brobecker
2008-07-18 23:13 ` Tom Tromey
2008-07-21 17:11 ` Stan Shebs
2008-07-21 0:30 ` Michael Snyder
2008-07-21 18:21 ` Paul Pluzhnikov
2008-07-21 18:32 ` Stan Shebs
2008-07-21 16:38 ` Michael Eager
2008-07-21 21:54 ` Stan Shebs
2008-07-31 22:04 ` Ian Lance Taylor
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=488405CE.3030901@netspace.net.au \
--to=rjshaw@netspace.net.au \
--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