From: Kevin Buettner <kevinb@redhat.com>
To: Tom de Vries <tdevries@suse.de>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] [gdb/testsuite] Add missing wait in gdb.multi/sched-multi-add-inferior.exp
Date: Fri, 9 Jan 2026 17:43:06 -0700 [thread overview]
Message-ID: <20260109174306.2727c387@f42-mesa-1> (raw)
In-Reply-To: <20260107111419.2516856-1-tdevries@suse.de>
On Wed, 7 Jan 2026 12:14:19 +0100
Tom de Vries <tdevries@suse.de> wrote:
> diff --git a/gdb/testsuite/gdb.multi/sched-multi-add-inferior.exp
> b/gdb/testsuite/gdb.multi/sched-multi-add-inferior.exp index
> 03d502a3cf3..4530960dd24 100644 ---
> a/gdb/testsuite/gdb.multi/sched-multi-add-inferior.exp +++
> b/gdb/testsuite/gdb.multi/sched-multi-add-inferior.exp @@ -66,6 +66,10 @@
> proc run_test { target_type_1 target_type_2 } { return 0
> }
>
> + # Block thread 2.1 from exiting function1, making sure that the
> breakpoint
> + # on the call to function2 won't trigger untill we unblock the
> thread.
Aside from the typo "untill", this commit is fine.
Approved with that fix.
Approved-by: Kevin Buettner <kevinb@redhat.com>
prev parent reply other threads:[~2026-01-10 0:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 11:14 Tom de Vries
2026-01-10 0:43 ` Kevin Buettner [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=20260109174306.2727c387@f42-mesa-1 \
--to=kevinb@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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