Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: Tom Tromey <tom@tromey.com>, Keith Seitz <keiths@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 00/11] [gdb/testsuite] Refactor exception handling
Date: Thu, 24 Sep 2026 18:08:34 +0200	[thread overview]
Message-ID: <56b49174-1d2b-4cf7-a1c2-43431efb80b6@suse.de> (raw)
In-Reply-To: <877bl34e9u.fsf@tromey.com>

On 9/2/26 9:57 PM, Tom Tromey wrote:
>>>>>> "Keith" == Keith Seitz <keiths@redhat.com> writes:
> 
> Keith> Thank you for simplifying this exception handling. I've sent
> Keith> a few little nits, but otherwise, this LGTM.
> 
> Keith> Reviewed-By: Keith Seitz <keiths@redhat.com>
> 
> Thanks for doing that.
> 
> I appreciate this series quite a bit.  I don't really get why Tcl came
> up with such a convoluted approach to what seems like a pretty normal
> thing to want to do; but oh well... anyway aside from the questions I
> sent and Keith's comments, I think it all looks good.

Thanks both for the reviews, much appreciated.

I've pushed all patches now, with the exception of "[PATCH 02/11] 
[gdb/testsuite] Fix return -level 2 bug in with_test_prefix".

The code in this patch got merged into another patch, and the test-case 
was not all that useful.  The new test-case 
gdb.testsuite/transparent-uplevel.exp covers the tested functionality 
much better.

Thanks,
- Tom

      reply	other threads:[~2026-09-24 16:09 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-24 13:58 Tom de Vries
2026-08-24 13:58 ` [PATCH 01/11] [gdb/testsuite] Normalize indentation in with_test_prefix Tom de Vries
2026-09-02 19:41   ` Tom Tromey
2026-09-04  9:48     ` Tom de Vries
2026-08-24 13:58 ` [PATCH 02/11] [gdb/testsuite] Fix return -level 2 bug " Tom de Vries
2026-09-02 19:46   ` Tom Tromey
2026-09-23 21:36     ` Tom de Vries
2026-09-24 14:18       ` Tom de Vries
2026-08-24 13:58 ` [PATCH 03/11] [gdb/testsuite] Simplify foreach_with_prefix Tom de Vries
2026-09-24 14:10   ` Tom de Vries
2026-08-24 13:58 ` [PATCH 04/11] [gdb/testsuite] Refactor exception handling in foreach_with_prefix Tom de Vries
2026-08-24 13:58 ` [PATCH 05/11] [gdb/testsuite] Add transparent_uplevel Tom de Vries
2026-09-01 16:16   ` Keith Seitz
2026-09-23 19:05     ` Tom de Vries
2026-08-24 13:58 ` [PATCH 06/11] [gdb/testsuite] Refactor exception handling Tom de Vries
2026-08-24 13:58 ` [PATCH 07/11] [gdb/testsuite] Refactor exception handling in gdb_expect Tom de Vries
2026-08-24 13:58 ` [PATCH 08/11] [gdb/testsuite] Refactor exception handling in gdb_test_multiple Tom de Vries
2026-08-25  7:29   ` Tom de Vries
2026-09-01 16:13   ` Keith Seitz
2026-09-24 16:03     ` Tom de Vries
2026-08-24 13:58 ` [PATCH 09/11] [gdb/testsuite] Refactor exception handling in lock_file_acquire/release Tom de Vries
2026-08-24 13:58 ` [PATCH 10/11] [gdb/testsuite] Refactor exception handling in tentative_rename Tom de Vries
2026-08-24 13:58 ` [PATCH 11/11] [gdb/testsuite] Refactor exception handling in with_stub_devices Tom de Vries
2026-09-01 16:10   ` Keith Seitz
2026-09-23 19:06     ` Tom de Vries
2026-09-01 17:07 ` [PATCH 00/11] [gdb/testsuite] Refactor exception handling Keith Seitz
2026-09-02 19:57   ` Tom Tromey
2026-09-24 16:08     ` Tom de Vries [this message]

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=56b49174-1d2b-4cf7-a1c2-43431efb80b6@suse.de \
    --to=tdevries@suse.de \
    --cc=gdb-patches@sourceware.org \
    --cc=keiths@redhat.com \
    --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