From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [PATCH v4 0/6] Fixes to gdb.threads/threadcrash.exp
Date: Fri, 8 Mar 2024 10:33:36 +0100 [thread overview]
Message-ID: <20240308093342.26745-1-tdevries@suse.de> (raw)
The test was recently pushed to master but it had a couple of small issues.
This is a quick series to fix the major issues.
Tested on arm-linux and x86_64-linux.
Changes for v4:
* added patch to remove unnecessary indentation
* added patch to simplify test_list usage
* added patch to fix check-readmore issues
* split off patch with _inferior_thread_count fix
* updated patch "Reduce gdb.threads/threadcrash.exp reliance on libc symbols"
to allow matching of libc symbols, if they're available.
* updated kfail patch to be both more specific, and only emit the kfail it it
actually triggers.
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: Use _inferior_thread_count in
gdb.threads/threadcrash.exp
gdb/testsuite: Reduce gdb.threads/threadcrash.exp reliance on libc
symbols
Tom de Vries (4):
gdb/testsuite: Reduce indentation in gdb.threads/threadcrash.exp
gdb/testsuite: Fix gdb.threads/threadcrash.exp with check-readmore
gdb/testsuite: Simplify gdb.threads/threadcrash.exp
gdb/testsuite: Add kfail in gdb.threads/threadcrash.exp on 32-bit arm
targets
gdb/testsuite/gdb.threads/threadcrash.exp | 236 ++++++++++++++--------
1 file changed, 150 insertions(+), 86 deletions(-)
base-commit: 5b95198e2e40b0301d37d989edc344a334c26b12
--
2.35.3
next reply other threads:[~2024-03-08 10:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 9:33 Tom de Vries [this message]
2024-03-08 9:33 ` [PATCH v4 1/6] gdb/testsuite: Reduce indentation in gdb.threads/threadcrash.exp Tom de Vries
2024-03-13 17:12 ` Tom Tromey
2024-03-08 9:33 ` [PATCH v4 2/6] gdb/testsuite: Fix gdb.threads/threadcrash.exp with check-readmore Tom de Vries
2024-03-13 17:17 ` Tom Tromey
2024-03-08 9:33 ` [PATCH v4 3/6] gdb/testsuite: Use _inferior_thread_count in gdb.threads/threadcrash.exp Tom de Vries
2024-03-08 9:33 ` [PATCH v4 4/6] gdb/testsuite: Simplify gdb.threads/threadcrash.exp Tom de Vries
2024-03-08 9:33 ` [PATCH v4 5/6] gdb/testsuite: Reduce gdb.threads/threadcrash.exp reliance on libc symbols Tom de Vries
2024-03-08 9:33 ` [PATCH v4 6/6] gdb/testsuite: Add kfail in gdb.threads/threadcrash.exp on 32-bit arm targets Tom de Vries
2024-03-08 10:24 ` Tom de Vries
2024-03-08 23:57 ` Thiago Jung Bauermann
2024-03-11 10:15 ` Tom de Vries
2024-03-11 18:10 ` Thiago Jung Bauermann
2024-03-11 23:03 ` Thiago Jung Bauermann
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=20240308093342.26745-1-tdevries@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).