From: Ruslan Kabatsayev <b7.10110111@gmail.com>
To: Gary Benson <gbenson@redhat.com>
Cc: psmith@gnu.org, gdb@sourceware.org
Subject: Re: gdb -batch always exits with status 0
Date: Fri, 17 Aug 2018 11:25:00 -0000 [thread overview]
Message-ID: <CAHEcG97NpFZNPphu+6va0i6AsC3Vk9OnXHi54bEWeQMzifVrdg@mail.gmail.com> (raw)
In-Reply-To: <20180817110354.GB32726@blade.nx>
On Fri, 17 Aug 2018 at 14:03, Gary Benson <gbenson@redhat.com> wrote:
>
> Paul Smith wrote:
> > On Thu, 2018-07-05 at 15:47 +0100, Gary Benson wrote:
> > > Would anybody object to my changing GDB's behaviour to terminate
> > > on the first error in batch mode?
> >
> > I would definitely not like this. Often I write batch files that
> > are used to collect information about cores (or running processes);
> > if some aspect of the core is not as I expect, or values are
> > optimized out, or some operation fails for whatever reason, I
> > definitely do not want my batch processing to stop. I want it to
> > continue so I can get as much information as possible.
> >
> > If a "stop on error" mode is needed then there should be a separate
> > option to GDB such as '-batch-fail' or whatever for that, IMO.
>
> Paul, Ruslan, would it be acceptable to you if I:
>
> 1) changed the default behaviour to exit 1 on the first error
> 2) added an option (e.g. -ignore-errors) to revert to the current
> behaviour.
Ideally, I'd like to have a more fine-grained way to choose which
commands' errors are to be ignored. But if it's much harder to
implement, the way you suggest is fine with me.
>
> Thanks,
> Gary
next prev parent reply other threads:[~2018-08-17 11:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-05 14:47 Gary Benson
2018-07-05 14:55 ` Ruslan Kabatsayev
2018-07-05 15:23 ` Paul Smith
2018-08-17 11:03 ` Gary Benson
2018-08-17 11:25 ` Ruslan Kabatsayev [this message]
2018-08-17 13:24 ` Paul Smith
2018-08-17 15:23 ` Gary Benson
2018-08-17 15:44 ` Ruslan Kabatsayev
2018-08-17 16:03 ` Gary Benson
2018-08-17 18:30 ` Pedro Alves
2018-08-22 9:07 ` Gary Benson
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=CAHEcG97NpFZNPphu+6va0i6AsC3Vk9OnXHi54bEWeQMzifVrdg@mail.gmail.com \
--to=b7.10110111@gmail.com \
--cc=gbenson@redhat.com \
--cc=gdb@sourceware.org \
--cc=psmith@gnu.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