From: "Marc Khouzam" <marc.khouzam@ericsson.com>
To: "Pedro Alves" <pedro@codesourcery.com>, <gdb@sourceware.org>
Cc: <jeremy.bennett@embecosm.com>
Subject: RE: Multiprogram teaser
Date: Tue, 29 Jul 2008 14:58:00 -0000 [thread overview]
Message-ID: <6D19CA8D71C89C43A057926FE0D4ADAA04291277@ecamlmw720.eamcs.ericsson.se> (raw)
In-Reply-To: <200807291431.26977.pedro@codesourcery.com>
> > We are currently preparing Eclipse/DSF to support
> multi-process debugging,
> > both locally and remotely.
> > We should have something workable for September.
> > But I'm not sure GDB will support this for linux or windows
> at that time.
>
> Remote multi-process for your OS, certainly; linux, we not
> there yet, but
> it's likelly; Windows, I may get around to work on it, but unless
> someone else steps up, I don't see it happen by September.
I think it would be nice from a GDB point-of-view, so, it would be nice
if someone from the community would step up :-)
> > Multi-program, gives me the impression that the debugged processes
> > will be started by GDB itself.
>
> Could also be attached processes. But, in extension to what you/we've
> been doing, we'll be able to attach to processes that run different
> execs/programs. Say attach to both /bin/cat and /bin/echo.
I had also imagined this as multi-process. You have a bunch of linux
processes already running and you can attach to multiple ones.
Like, say, vi and emacs. So, multi-process debugging would work for
long-lived processes.
I thought multi-program would launch different programs, which could
then be short-lived. But that's how I imagined it...
Marc
next prev parent reply other threads:[~2008-07-29 14:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 2:29 Stan Shebs
2008-07-29 8:18 ` Michael Snyder
2008-07-29 13:14 ` Jeremy Bennett
2008-07-29 13:34 ` Marc Khouzam
2008-07-29 13:51 ` Pedro Alves
2008-07-29 14:58 ` Marc Khouzam [this message]
2008-07-29 14:12 ` Stan Shebs
2008-07-29 16:02 ` Marc Khouzam
2008-07-30 17:21 ` Tom Tromey
2008-07-30 17:43 ` Tom Tromey
2008-07-30 18:07 ` Stan Shebs
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=6D19CA8D71C89C43A057926FE0D4ADAA04291277@ecamlmw720.eamcs.ericsson.se \
--to=marc.khouzam@ericsson.com \
--cc=gdb@sourceware.org \
--cc=jeremy.bennett@embecosm.com \
--cc=pedro@codesourcery.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