From: Eli Zaretskii <eliz@gnu.org>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: gdb-patches@sourceware.org, dje@google.com, palves@redhat.com
Subject: Re: [PATCH v2] Add convenience variable $_exitsignal
Date: Tue, 18 Jun 2013 19:02:00 -0000 [thread overview]
Message-ID: <83txkvqmef.fsf@gnu.org> (raw)
In-Reply-To: <m3ehbzqmsn.fsf@redhat.com>
> From: Sergio Durigan Junior <sergiodj@redhat.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, Doug Evans <dje@google.com>,
> Pedro Alves <palves@redhat.com>
> Date: Tue, 18 Jun 2013 15:46:48 -0300
>
> diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
> index e6ec4ff..a445b1a 100644
> --- a/gdb/doc/gdb.texinfo
> +++ b/gdb/doc/gdb.texinfo
> @@ -9734,8 +9734,15 @@ to match the format in which the data was printed.
>
> @item $_exitcode
> @vindex $_exitcode@r{, convenience variable}
> -The variable @code{$_exitcode} is automatically set to the exit code when
> -the program being debugged terminates.
> +When the program being debugged terminates normally, @value{GDBN}
> +automatically sets this variable to the exit code of the program, and
> +clears @code{$_exitsignal}.
> +
> +@item $_exitsignal
> +@vindex $_exitsignal@r{, convenience variable}
> +When the program being debugged dies due to an uncaught signal,
> +@value{GDBN} automatically sets this variable to that signal's number,
> +and clears @code{$_exitcode}.
This is good, but I wonder whether the meaning of "clears $_exitcode"
will be sufficiently clear (pun intended) to the reader. You mean to
say that the variable will be void, right?
Thanks.
next prev parent reply other threads:[~2013-06-18 18:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 18:55 Sergio Durigan Junior
2013-06-18 19:02 ` Eli Zaretskii [this message]
2013-06-18 19:07 ` Sergio Durigan Junior
2013-06-18 19:16 ` Eli Zaretskii
2013-06-18 19:44 ` Sergio Durigan Junior
2013-06-19 10:56 ` Pedro Alves
2013-07-18 16:50 ` Tom Tromey
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=83txkvqmef.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=sergiodj@redhat.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