From: Marco Barisione via Gdb-patches <gdb-patches@sourceware.org>
To: Tom de Vries <tdevries@suse.de>
Cc: Tom Tromey <tom@tromey.com>,
GDB patches mailing list <gdb-patches@sourceware.org>
Subject: Re: [RFC][gdb/cli] Ignore error in gdb command script
Date: Tue, 18 May 2021 12:12:47 +0100 [thread overview]
Message-ID: <44B64C9E-9E19-47BD-80CD-0C660C7A9D94@undo.io> (raw)
In-Reply-To: <20210518095958.GA22771@delia>
On 18 May 2021, at 10:59, Tom de Vries <tdevries@suse.de> wrote:
> Hi,
>
> While trying to reproduce a failing test-case from the testsuite on the
> command line using a gdb command script, I ran into the problem that a command
> failed which stopped script execution.
>
> I could work around this by splitting the script at each error, but I realized
> it would be nice if I could tell gdb to ignore the error.
>
> Inspired by make, I chose the '-' prefix.
As MI commands are prefixed by “-“, isn’t there a risk of confusion?
There’s also a “-” command (see tui/tui-win.c) which will stop working with
your patch.
--
Marco Barisione
next prev parent reply other threads:[~2021-05-18 11:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 9:59 Tom de Vries
2021-05-18 11:12 ` Marco Barisione via Gdb-patches [this message]
2021-05-18 13:57 ` Tom de Vries
2021-05-18 14:10 ` Simon Marchi via Gdb-patches
2021-05-18 14:42 ` Tom Tromey
2021-05-18 15:16 ` Tom de Vries
2021-05-18 15:32 ` Tom Tromey
2021-05-19 6:25 ` [PATCH][gdb/cli] Add ignore-errors command Tom de Vries
2021-05-19 7:32 ` Andreas Schwab
2021-05-19 7:36 ` Tom de Vries
2021-05-18 19:16 ` [RFC][gdb/cli] Ignore error in gdb command script Philippe Waroquiers via Gdb-patches
2021-05-18 21:59 ` Tom de Vries
2021-05-20 8:02 ` Philippe Waroquiers via Gdb-patches
2021-05-20 15:01 ` Simon Marchi via Gdb-patches
2021-05-18 14:23 ` Andrew Burgess
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=44B64C9E-9E19-47BD-80CD-0C660C7A9D94@undo.io \
--to=gdb-patches@sourceware.org \
--cc=mbarisione@undo.io \
--cc=tdevries@suse.de \
--cc=tom@tromey.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