From: Guinevere Larsen <blarsen@redhat.com>
To: gdb-patches@sourceware.org
Cc: Guinevere Larsen <blarsen@redhat.com>
Subject: [PATCH v2 0/2] Fixes to gdb.threads/threadcrash.exp
Date: Tue, 13 Feb 2024 12:09:23 +0100 [thread overview]
Message-ID: <20240213110924.123394-2-blarsen@redhat.com> (raw)
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 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 | 32 +++++++++++------------
1 file changed, 15 insertions(+), 17 deletions(-)
--
2.43.0
next reply other threads:[~2024-02-13 11:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 11:09 Guinevere Larsen [this message]
2024-02-13 11:09 ` [PATCH v2 1/2] gdb/testsuite: fix gdb.threads/threadcrash.exp on 32-bit arm targets Guinevere Larsen
2024-02-15 14:31 ` Lancelot SIX
2024-02-13 11:09 ` [PATCH v2 2/2] gdb/testsuite: reduce gdb.threads/threadcrash.exp reliance on libc symbols Guinevere Larsen
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=20240213110924.123394-2-blarsen@redhat.com \
--to=blarsen@redhat.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).