From: Guinevere Larsen <blarsen@redhat.com>
To: Guinevere Larsen <blarsen@redhat.com>,
Gdb-patches <gdb-patches@sourceware.org>
Cc: Tom de Vries <tdevries@suse.de>
Subject: [PING][PATCH v3 0/2] Fixes to gdb.threads/threadcrash.exp
Date: Wed, 6 Mar 2024 14:02:39 +0100 [thread overview]
Message-ID: <11f36924-0919-4240-82d0-1d0cfc2a862a@redhat.com> (raw)
In-Reply-To: <20240214091712.223928-2-blarsen@redhat.com>
On 14/02/2024 10:17, Guinevere Larsen wrote:
> The test was recently pushed to master but it had a couple of small
> issues. This is a quick series to fix the 2 major issues that were
> brought up to my attention.
>
> Changes for v3:
> * use get_valueof to get thread count, to stop a failure on Linaro's CI.
>
> Changes for v2:
> * changed xfail from patch 1 to a kfail
>
> Guinevere Larsen (2):
> gdb/testsuite: fix gdb.threads/threadcrash.exp on 32-bit arm targets
> gdb/testsuite: reduce gdb.threads/threadcrash.exp reliance on libc
> symbols
>
> gdb/testsuite/gdb.threads/threadcrash.exp | 46 +++++++----------------
> 1 file changed, 14 insertions(+), 32 deletions(-)
>
Ping!
Adding Tom de Vries to CC since he commented on one of the related bugs
(testsuite/31293)
--
Cheers,
Guinevere Larsen
She/Her/Hers
prev parent reply other threads:[~2024-03-06 13:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 9:17 [PATCH " Guinevere Larsen
2024-02-14 9:17 ` [PATCH v3 1/2] gdb/testsuite: fix gdb.threads/threadcrash.exp on 32-bit arm targets Guinevere Larsen
2024-02-15 14:37 ` Lancelot SIX
2024-03-08 10:01 ` Tom de Vries
2024-03-08 10:12 ` Tom de Vries
2024-02-14 9:17 ` [PATCH v3 2/2] gdb/testsuite: reduce gdb.threads/threadcrash.exp reliance on libc symbols Guinevere Larsen
2024-03-06 17:16 ` Tom de Vries
2024-03-07 9:11 ` Guinevere Larsen
2024-03-07 18:23 ` Tom de Vries
2024-03-06 13:02 ` Guinevere Larsen [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=11f36924-0919-4240-82d0-1d0cfc2a862a@redhat.com \
--to=blarsen@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).