From: Stan Shebs <stan@codesourcery.com>
To: Michael Eager <eager@eagercon.com>
Cc: gdb@sourceware.org
Subject: Re: Towards multiprocess GDB
Date: Mon, 21 Jul 2008 21:54:00 -0000 [thread overview]
Message-ID: <4884D62B.8040904@codesourcery.com> (raw)
In-Reply-To: <4884B40C.3010707@eagercon.com>
Michael Eager wrote:
> I would like to see GDB become a multi-process, multi-target, multi-
> architecture debugger.
I agree that this should be the ultimate outcome, and I keep it in mind
when thinking about specific subsystems. After all, that was one of the
main reasons for the long and painful transition from random
preprocessor macros to gdbarch objects. Poking around the web pages and
wiki, I don't see anything actually saying that anywhere, although most
GDBers I've talked to in person are in agreement. Time for a new
long-term roadmap?
Stan
next prev parent reply other threads:[~2008-07-21 18:32 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 [this message]
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=4884D62B.8040904@codesourcery.com \
--to=stan@codesourcery.com \
--cc=eager@eagercon.com \
--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