From: Pedro Alves <pedro@palves.net>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/5] Adjust/fix gdb.thread/pthreads.exp for Cygwin
Date: Wed, 20 Sep 2023 18:59:54 +0100 [thread overview]
Message-ID: <20230920175959.2305271-1-pedro@palves.net> (raw)
This set of patches improves gdb.thread/pthreads.exp when testing
against Cygwin. The test still won't pass cleanly [1] without some GDB
fixes (which I plan on submitting later at some point), but if you run
it against the GDB distributed with Cygwin, at least, it passes (they
have some local GDB patches missing upstream).
[1] - it fails with:
FAIL: gdb.threads/pthreads.exp: Stopped with a ^C (timeout)
WARNING: Could not stop child with ^C; skipping rest of tests.
Pedro Alves (5):
gdb.threads/pthreads.c, K&R -> ANSI function style
Fix gdb.threads/pthreads.c formatting
Fix gdb.threads/pthreads.exp error handling/printing
In gdb.threads/pthreads.c, handle pthread_attr_setscope ENOTSUP
Adjust gdb.thread/pthreads.exp for Cygwin
gdb/testsuite/gdb.threads/pthreads.c | 86 ++++++++++++++++----------
gdb/testsuite/gdb.threads/pthreads.exp | 14 ++---
2 files changed, 60 insertions(+), 40 deletions(-)
base-commit: 093da43d2adb4497dfec8afbb4eeaf2425668fdd
--
2.34.1
next reply other threads:[~2023-09-20 18:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 17:59 Pedro Alves [this message]
2023-09-20 17:59 ` [PATCH 1/5] gdb.threads/pthreads.c, K&R -> ANSI function style Pedro Alves
2023-09-20 17:59 ` [PATCH 2/5] Fix gdb.threads/pthreads.c formatting Pedro Alves
2023-09-20 17:59 ` [PATCH 3/5] Fix gdb.threads/pthreads.exp error handling/printing Pedro Alves
2023-09-20 17:59 ` [PATCH 4/5] In gdb.threads/pthreads.c, handle pthread_attr_setscope ENOTSUP Pedro Alves
2023-09-20 17:59 ` [PATCH 5/5] Adjust gdb.thread/pthreads.exp for Cygwin Pedro Alves
2023-09-21 19:21 ` [PATCH 0/5] Adjust/fix " Tom Tromey
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=20230920175959.2305271-1-pedro@palves.net \
--to=pedro@palves.net \
--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).