Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Gary Benson <gbenson@redhat.com>
Cc: Tom Tromey <tom@tromey.com>,  gdb-patches@sourceware.org
Subject: Re: [PATCH] Indicate batch mode failures by exiting with nonzero status
Date: Sun, 19 Aug 2018 15:35:00 -0000	[thread overview]
Message-ID: <87bm9ygyiv.fsf@tromey.com> (raw)
In-Reply-To: <20180817105923.GA32726@blade.nx> (Gary Benson's message of "Fri,	17 Aug 2018 11:59:24 +0100")

>>>>> "Gary" == Gary Benson <gbenson@redhat.com> writes:

>> Also, why just the last command?  I mean, I guess I don't really know
>> what I would expect, but maybe if any command failed, gdb should exit?

Gary> That was my thinking, to have GDB exit 1 on the first error in batch
Gary> mode, but people objected; see the followups to:

Oh, ok, sorry for wading into an already open issue without the
background.

On reflection perhaps I'm overthinking it.  It seems to me that it is
fine for these command line options to be defined based on whatever
seems convenient.

For "real" scripting, a script file could be used.  Maybe we could
finally land that try/catch patch, or the ignore-errors command.
Or, longer term, finally make it possible to really script with Python.

Tom


  parent reply	other threads:[~2018-08-19 15:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-16 13:23 Gary Benson
2018-08-16 23:46 ` Tom Tromey
2018-08-17 10:59   ` Gary Benson
2018-08-17 14:28     ` Pedro Alves
2018-08-17 15:38       ` Gary Benson
2018-08-19 15:35     ` Tom Tromey [this message]
2018-08-25 19:52       ` Philippe Waroquiers

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=87bm9ygyiv.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gbenson@redhat.com \
    --cc=gdb-patches@sourceware.org \
    /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