From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [v7] multi-executable support
Date: Mon, 12 Oct 2009 19:09:00 -0000 [thread overview]
Message-ID: <83r5t8ig10.fsf@gnu.org> (raw)
In-Reply-To: <200910120226.08575.pedro@codesourcery.com>
> From: Pedro Alves <pedro@codesourcery.com>
> Date: Mon, 12 Oct 2009 02:26:08 +0100
> Cc: Eli Zaretskii <eliz@gnu.org>
>
> Here's the updated patch with docs fixed per review.
Thanks.
> Index: src/gdb/NEWS
> ===================================================================
> --- src.orig/gdb/NEWS 2009-10-11 19:45:41.000000000 +0100
> +++ src/gdb/NEWS 2009-10-11 20:33:58.000000000 +0100
> @@ -3,6 +3,40 @@
This part is fine.
> +may be retained after a process exits. Inferiors have unique
> +identifiers that are different from process ids. Usually each
> +inferior will also have its own distinct address space, although some
> +embedded targets may have several inferiors running in different parts
> +of a single address space. For example, debugging programs that call
> +@code{vfork}, or embedded targets that may have several inferiors
> +running in different parts of a single address space.
The last two sentences say the same about embedded targets in two
slightly different ways. Suggest to merge into a single sentence.
> +inferior. Restarting the inferior after the @code{exec} call, with
> +e.g. the @code{run} command, restarts the executable the process was
^^^^^
This needs either a @: or a comma after "e.g.", to avoid it being
typeset as an end of a sentence.
Okay with these changes.
next prev parent reply other threads:[~2009-10-12 19:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-05 15:59 [v6] " Pedro Alves
2009-10-05 21:57 ` Eli Zaretskii
2009-10-06 12:14 ` Pedro Alves
2009-10-06 14:29 ` Eli Zaretskii
2009-10-12 1:26 ` [v7] " Pedro Alves
2009-10-12 19:09 ` Eli Zaretskii [this message]
2009-10-13 13:40 ` [v8] " Pedro Alves
2009-10-14 3:03 ` Joel Brobecker
2009-10-14 15:16 ` Pedro Alves
2009-10-14 15:28 ` Joel Brobecker
2009-10-14 16:25 ` Tom Tromey
2009-10-14 16:48 ` Pedro Alves
2009-10-14 17:41 ` Tom Tromey
2009-10-06 5:13 ` [v6] " Sérgio Durigan Júnior
2009-10-06 13:55 ` 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=83r5t8ig10.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