Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Paul_Koning@Dell.com
Cc: tromey@redhat.com, daniel.gutson@tallertechnologies.com,
	       gdb-patches@sourceware.org
Subject: Re: specifying gdb's exit code
Date: Wed, 23 Apr 2014 17:46:00 -0000	[thread overview]
Message-ID: <5357FC48.7030206@redhat.com> (raw)
In-Reply-To: <0532FE81-AE98-4E34-B48B-D82091FC6CF2@dell.com>

On 04/23/2014 06:35 PM, Paul_Koning@Dell.com wrote:
> 
> On Apr 23, 2014, at 1:29 PM, Pedro Alves <alves.ped@gmail.com> wrote:

>> Would it be good if the online help and the manual agreed a bit
>> more?  The manual says "quit [expression]":

>> To exit @value{GDBN}, use the @code{quit} command (abbreviated
>> @code{q}), or type an end-of-file character (usually @kbd{Ctrl-d}).  If you
>> do not supply @var{expression}, @value{GDBN} will terminate normally;
>> otherwise it will terminate using the result of @var{expression} as the
>> error code.
>> @end table
> 
> I think it should say “exit code” rather than “error code”.  Whether a given expression value is the code for an error depends on the value and on the host OS.

Agreed.  I'd even call that an obvious change to the manual.

-- 
Pedro Alves


  reply	other threads:[~2014-04-23 17:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAF5HaEVTZAxc0FNR9GnGNKJqxGSrbQaTfZ7ZRMoueTg6jQyL8A@mail.gmail.com>
     [not found] ` <CAF5HaEWDv6Gb2m-iDpzcM4y_ybkT46R1b96xxdS9buLHbsgwRQ@mail.gmail.com>
     [not found]   ` <CADPb22RS0J3X8hcBiUiDPp62RYiKPE4vCSPV5WEMUF01KzsiLg@mail.gmail.com>
     [not found]     ` <CAF5HaEV3wMHXfk3jLmbY-E6XAaZSmBRhzDjo2BvhQ7NbvvCtZQ@mail.gmail.com>
2014-04-17 21:52       ` Daniel Gutson
2014-04-22 12:37         ` Daniel Gutson
2014-04-23 17:11         ` Tom Tromey
2014-04-23 17:29           ` Eli Zaretskii
2014-04-23 17:29           ` Pedro Alves
2014-04-23 17:36             ` Paul_Koning
2014-04-23 17:46               ` Pedro Alves [this message]
2014-04-23 17:49             ` Tom Tromey
2014-04-23 17:57               ` Pedro Alves
2014-04-25 15:44                 ` Tom Tromey
2014-04-23 18:17               ` Paul_Koning
2014-04-23 18:23                 ` Tom Tromey
2014-04-23 20:53                   ` Daniel Gutson
2014-04-23 20:55                     ` Daniel Gutson

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=5357FC48.7030206@redhat.com \
    --to=palves@redhat.com \
    --cc=Paul_Koning@Dell.com \
    --cc=daniel.gutson@tallertechnologies.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@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