From: "Marc Khouzam" <marc.khouzam@ericsson.com>
To: <jeremy.bennett@embecosm.com>, <gdb@sourceware.org>
Subject: RE: Multiprogram teaser
Date: Tue, 29 Jul 2008 13:34:00 -0000 [thread overview]
Message-ID: <6D19CA8D71C89C43A057926FE0D4ADAA04291275@ecamlmw720.eamcs.ericsson.se> (raw)
In-Reply-To: <1217319521.2841.18.camel@thomas>
Hi,
> This looks good, but points up the limitations of line based debugging
> once you have to handle multiple processors. Realistically
> this sort of
> approach is going to need some sort of windowing environment
> to separate
> out the information. Do you have a view of how this might look inside
> gdbtui or ddd or Eclipse?
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.
Note that I say "multi-process" and not "multi-program". The reason
is that what we are doing will support multi-debugging using
the 'attach' command. So, you can imagine having a running system
with many processes, and you could then attach to multiple ones.
Multi-program, gives me the impression that the debugged processes
will be started by GDB itself. I believe that is what Stan is
aiming at, right? This would also fit in Eclipse/DSF, but is not
in our short term planning. But maybe later...
Marc
next prev parent reply other threads:[~2008-07-29 13:14 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 [this message]
2008-07-29 13:51 ` Pedro Alves
2008-07-29 14:58 ` Marc Khouzam
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=6D19CA8D71C89C43A057926FE0D4ADAA04291275@ecamlmw720.eamcs.ericsson.se \
--to=marc.khouzam@ericsson.com \
--cc=gdb@sourceware.org \
--cc=jeremy.bennett@embecosm.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