From: Eli Zaretskii <eliz@gnu.org>
To: Hui Zhu <teawater@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA/RFC/DOC] Fix the different between behavior of "detach inferior" "kill inferior" and doc
Date: Fri, 30 Jul 2010 08:45:00 -0000 [thread overview]
Message-ID: <83y6ctbbpw.fsf@gnu.org> (raw)
In-Reply-To: <AANLkTi=+Xmn+fVFD9KVzGJA0MF8_XB4KHZCCOHPF=W=z@mail.gmail.com>
> From: Hui Zhu <teawater@gmail.com>
> Date: Fri, 30 Jul 2010 16:13:42 +0800
> Cc: Eli Zaretskii <eliz@gnu.org>
>
> So I make a patch to update the doc.
>
> Thanks,
> Hui
>
> 2010-07-30 Hui Zhu <teawater@gmail.com>
>
> * gdb.texinfo (Inferiors and Programs): Update the introduce of
> "detach inferior" and "kill inferior".
>
>
> ---
> doc/gdb.texinfo | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> --- a/doc/gdb.texinfo
> +++ b/doc/gdb.texinfo
> @@ -2481,12 +2481,12 @@ using the @w{@code{kill inferior}} comma
> @kindex detach inferior @var{infno}
> @item detach inferior @var{infno}
> Detach from the inferior identified by @value{GDBN} inferior number
> -@var{infno}, and remove it from the inferior list.
> +@var{infno}.
>
> @kindex kill inferior @var{infno}
> @item kill inferior @var{infno}
> Kill the inferior identified by @value{GDBN} inferior number
> -@var{infno}, and remove it from the inferior list.
> +@var{infno}.
> @end table
Assuming that the code behaves as intended (i.e. this isn't a bug), I
suggest the following text instead:
Kill the inferior identified by @value{GDBN} inferior number
@var{infno}. Note that the inferior's entry still stays on the list
of inferiors shown by @code{info inferiors}, but its Description will
show @samp{<null>}.
and similarly for "detach".
Thanks.
next prev parent reply other threads:[~2010-07-30 8:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-30 8:14 Hui Zhu
2010-07-30 8:45 ` Eli Zaretskii [this message]
2010-07-30 9:02 ` Hui Zhu
2010-07-30 9:57 ` Pedro Alves
2010-07-30 14:57 ` Hui Zhu
2010-07-30 9:38 ` 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=83y6ctbbpw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=teawater@gmail.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