Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH 03/11] [gdb/testsuite] Simplify foreach_with_prefix
Date: Thu, 24 Sep 2026 16:10:13 +0200	[thread overview]
Message-ID: <713687b7-7a61-463f-aac1-ccf59cc1c589@suse.de> (raw)
In-Reply-To: <20260824135855.1195963-4-tdevries@suse.de>

On 8/24/26 3:58 PM, Tom de Vries wrote:
> Move the foreach into the catch:
> ...
>      set code [catch {
>          foreach myvar $list {
>              with_test_prefix "$var=$myvar" {
>                  uplevel 1 $body
>              }
>          }
>      } result]
> ...
> to let foreach handle break and continue, allowing us to handle the catch
> result in the usual way.
> 
> Likewise in foreach_mi_ui_mode.

I've pushed this and the following patch ( [PATCH 04/11] [gdb/testsuite] 
Refactor exception handling in foreach_with_prefix ), as well as three 
more which were not part of this series ( 
https://sourceware.org/pipermail/gdb-patches/2026-September/230612.html ):
- a patch further simplifying foreach_with_prefix
- a patch adding another test-case for foreach_with_prefix
- a patch further simplifying foreach_mi_ui_mode.

Thanks,
- Tom

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

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-24 13:58 [PATCH 00/11] [gdb/testsuite] Refactor exception handling 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 [this message]
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

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=713687b7-7a61-463f-aac1-ccf59cc1c589@suse.de \
    --to=tdevries@suse.de \
    --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