From: Ian Lance Taylor <ian@airs.com>
To: Stan Shebs <stanshebs@earthlink.net>
Cc: gdb@sourceware.org
Subject: Re: Towards multiprocess GDB
Date: Thu, 31 Jul 2008 22:04:00 -0000 [thread overview]
Message-ID: <m3myjxyg7l.fsf@gossamer.airs.com> (raw)
In-Reply-To: <4880FFA8.3080600@earthlink.net> (Stan Shebs's message of "Fri\, 18 Jul 2008 13\:40\:08 -0700")
Stan Shebs <stanshebs@earthlink.net> writes:
> 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.
>
> To put it simply, the goal of the project is to make this command work
> in some useful way:
>
> gdb prog1 prog2 pid2 prog3 prog4
I am certainly interested in having this happen. I just want to add
that in the cases I most care about the different programs are
actually running on different machines. That should fall out pretty
naturally, using gdbserver, from this work if done right; I'm just
chiming in now to make sure that that capability is considered as a
goal from the start. Thanks.
Ian
prev parent reply other threads:[~2008-07-31 20:03 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
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 [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=m3myjxyg7l.fsf@gossamer.airs.com \
--to=ian@airs.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