Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Marc Khouzam" <marc.khouzam@ericsson.com>
To: "Stan Shebs" <stan@codesourcery.com>
Cc: <jeremy.bennett@embecosm.com>, <gdb@sourceware.org>
Subject: RE: Multiprogram teaser
Date: Tue, 29 Jul 2008 16:02:00 -0000	[thread overview]
Message-ID: <6D19CA8D71C89C43A057926FE0D4ADAA0429127B@ecamlmw720.eamcs.ericsson.se> (raw)
In-Reply-To: <488F24C7.1000007@codesourcery.com>


> By "multiprogram" I mean that there can be several different 
> executables, each with its own code, symbols, etc. There's no 
> assumption 
> about how GDB interacts with the running targets created from the 
> executables; it could launch, attach, do target remote, etc.
> 
> It's orthogonal to "multiprocess" debugging because you could 
> have one 
> executable and be debugging a half-dozen processes created by 
> multiple 
> runs of the executable. You could also have a single process whose 
> address space includes several different executables, each at a 
> different address.
> 
> "Multiprocess" is often taken to mean "multiprogram" as well, 
> presumably 
> because the case of one executable and multiple processes is not that 
> interesting in practice.

From an Eclipse GUI point-of-view (user point-of-view), I get
the impression that the two concepts could be treated 
the same.  The user would be interested in debugging a running/runnable
process. But maybe I'm over-simplifying...

Marc


  reply	other threads:[~2008-07-29 15:47 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
2008-07-29 14:12     ` Stan Shebs
2008-07-29 16:02       ` Marc Khouzam [this message]
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=6D19CA8D71C89C43A057926FE0D4ADAA0429127B@ecamlmw720.eamcs.ericsson.se \
    --to=marc.khouzam@ericsson.com \
    --cc=gdb@sourceware.org \
    --cc=jeremy.bennett@embecosm.com \
    --cc=stan@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