Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Tom Tromey <tom@tromey.com>,
	Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH][gdb/cli] Add ignore-errors command
Date: Wed, 19 May 2021 09:36:01 +0200	[thread overview]
Message-ID: <88164e8f-52fa-d5cf-e6d6-2e546bbce6c2@suse.de> (raw)
In-Reply-To: <87wnrv89hh.fsf@igel.home>

On 5/19/21 9:32 AM, Andreas Schwab wrote:
> On Mai 19 2021, Tom de Vries wrote:
> 
>> This patch adds native ignore-errors support (so no python needed).
> 
> This makes abbreviations of "ignore" abigous.

Indeed.

Can already be demonstrated using the system gdb on openSUSE:
...
(gdb) ign<TAB>
Ambiguous command "ign": ignore, ignore-errors.
(gdb)
...

Thanks,
- Tom


  reply	other threads:[~2021-05-19  7:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-18  9:59 [RFC][gdb/cli] Ignore error in gdb command script 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
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 [this message]
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=88164e8f-52fa-d5cf-e6d6-2e546bbce6c2@suse.de \
    --to=tdevries@suse.de \
    --cc=gdb-patches@sourceware.org \
    --cc=schwab@linux-m68k.org \
    --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