Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stan Shebs <stan@codesourcery.com>
Cc: pedro@codesourcery.com, gdb-patches@sourceware.org
Subject: Re: [RFA 01/08] multi-process support: struct inferior (alternate  manual content)
Date: Wed, 17 Sep 2008 03:17:00 -0000	[thread overview]
Message-ID: <u63ovpilf.fsf@gnu.org> (raw)
In-Reply-To: <48D0501E.2060802@codesourcery.com>

> Date: Tue, 16 Sep 2008 17:32:30 -0700
> From: Stan Shebs <stan@codesourcery.com>
> CC: gdb-patches@sourceware.org
> 
> Here is an alternate phrasing for GDB's new inferior objects, 
> wordsmithed so that it (mostly) makes sense with just Pedro's patches, 
> and also so that it can be easily expanded into the full multi-exec 
> section in the near future. To repeat from my last comment, I don't 
> think we need to be really polished just yet, the single-exec + 
> multi-inferior case is just a transitional stage of limited interest.
> 
> Stan
> 
> 2008-09-16  Stan Shebs  <stan@codesourcery.com>
> 
>     * gdb.texinfo (Inferiors): New section.

Thanks, this is okay.

> +                                An inferior typically corresponds to a
> + process, but is more general and applies also to targets that do not
> + have processes.

An example of an inferior that is not a process will help here.

Also, please make sure there are 2 spaces between each 2 sentences.


  reply	other threads:[~2008-09-17  3:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-12 15:38 [RFA 01/08] multi-process support: struct inferior Pedro Alves
2008-09-12 16:08 ` Eli Zaretskii
2008-09-12 16:08 ` Eli Zaretskii
2008-09-12 17:21   ` Pedro Alves
2008-09-12 20:00     ` Eli Zaretskii
2008-09-16 22:05       ` Stan Shebs
2008-09-17  0:33 ` [RFA 01/08] multi-process support: struct inferior (alternate manual content) Stan Shebs
2008-09-17  3:17   ` Eli Zaretskii [this message]
2008-09-18 22:46 ` [RFA 01/08] multi-process support: struct inferior Daniel Jacobowitz
2008-09-22 15:35   ` 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=u63ovpilf.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.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