Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [v4 2/2] multi-executable support
Date: Sat, 05 Sep 2009 20:16:00 -0000	[thread overview]
Message-ID: <838wgt409z.fsf@gnu.org> (raw)
In-Reply-To: <200909051941.12181.pedro@codesourcery.com>

> From: Pedro Alves <pedro@codesourcery.com>
> Date: Sat, 5 Sep 2009 19:41:11 +0100
> 
> > So "symbol space" is actually a synonym for a "program", i.e. the set
> > of code, data, and symbolic debug info that is the result of linking
> > an executable? then why not call it a "program"?  
> 
> I would like that, but I'm not sure if it is correct.  If
> it is, great, I'm very glad to simplify.
> 
> I actually don't know the exact definition of what is a "program".
> Are the code, data, symbolic debug info of the load shared libraries
> (and of other sources, e.g., added with add-symbol-file) part of the
> program as well, or is the program considered the main executable
> only?  I had the feeling that in GDB speak, it was the latter case.
> If not, I'd be glad to s/sspaces/programs/g.
> 
> Let me try to give concrete examples to show why I got to where
> I am, and then I hope you'll be able to tell me (from the user's
> perspective) with a stronger opinion, that I should really expose
> sspaces as "programs" to the user, or not.  Please be patient,
> the email is long, but it's mostly just pastes of usage examples.

Thanks for making this effort to explain things.  It's late down here,
and I'm after a long day of debugging the GDB build for DJGPP.  I need
to think about this with a fresh mind, so this will have to wait for
tomorrow.

For now, let me ask just one question.  I believe answering it will go
a long way towards defining the best paradigm and hence names for
these features.

Here's my question: Why do we need a container for inferiors (that you
call sspace)?  I understand why we need a way of starting another
inferior _in_addition_to_ the existing ones (as opposed to
_instead_of_ the existing one).  But wouldn't it be enough to have one
command -- "add-inferior", say -- to provide the same set of features
you want, i.e. the ability to debug several inferiors at the same
time?

IOW, I don't understand why we need to group inferiors by sspaces.

TIA


  reply	other threads:[~2009-09-05 20:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-03  2:49 [v4 0/2] " Pedro Alves
2009-09-03  2:51 ` [v4 1/2] " Pedro Alves
2009-09-03  2:53 ` [v4 2/2] " Pedro Alves
2009-09-03 18:31   ` Eli Zaretskii
2009-09-03 18:40     ` Pedro Alves
2009-09-03 20:37       ` Eli Zaretskii
2009-09-05 18:41     ` Pedro Alves
2009-09-05 20:16       ` Eli Zaretskii [this message]
2009-09-05 21:15         ` Pedro Alves
2009-09-06  3:16           ` Eli Zaretskii
2009-09-08 15:16             ` [v4 2/2] multi-executable support (new v5 patch included) Pedro Alves
2009-09-08 19:16               ` Eli Zaretskii
2009-10-05 15:22                 ` Pedro Alves
2009-09-09  6:40               ` Vladimir Prus
2009-09-09 10:28                 ` Pedro Alves
2009-09-03  2:56 ` [v4 0/2] multi-executable support (.gz) Pedro Alves

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=838wgt409z.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --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