From: Tom Tromey <tom@tromey.com>
To: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
Cc: Tom Tromey <tom@tromey.com>
Subject: Re: [RFC][gdb/cli] Ignore error in gdb command script
Date: Tue, 18 May 2021 08:42:59 -0600 [thread overview]
Message-ID: <87im3g14ss.fsf@tromey.com> (raw)
In-Reply-To: <453ffcaa-2a21-62a7-d449-28c7c187231a@polymtl.ca> (Simon Marchi via Gdb-patches's message of "Tue, 18 May 2021 10:10:44 -0400")
>>>>> "Simon" == Simon Marchi via Gdb-patches <gdb-patches@sourceware.org> writes:
Simon> That sounds useful. I think that "ignore-errors" is a good initial
Simon> name, because it's clear and self-describing. We can always find and
Simon> add a short alias later.
Fedora has shipped a Python implementation of exactly this for a while now.
So, +1 for this name and approach from me.
One question is whether it should catch 'quit'. I tend to think not but
it should be considered.
There is some other prior art too:
https://sourceware.org/bugzilla/show_bug.cgi?id=8487
ignore-errors covers all the uses I've ever wanted personally, though,
so I think it would be fine to just go with that. However if someone is
feeling more maximal, try-catch would also be an ok addition.
Tom
next prev parent reply other threads:[~2021-05-18 14:43 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
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 [this message]
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=87im3g14ss.fsf@tromey.com \
--to=tom@tromey.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