aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPedro Alves <pedro@palves.net>2023-09-15 20:06:37 +0100
committerPedro Alves <pedro@palves.net>2023-09-27 15:28:40 +0100
commitb57264372264ebe6a8115028aa15c81af4fd98f1 (patch)
tree96d9e073cecc21a8916cb7f5be804cff7ea85886
parentf3e4716cc534f9521bd97abc400d8e8f0e73ea6a (diff)
downloadbinutils-b57264372264ebe6a8115028aa15c81af4fd98f1.zip
binutils-b57264372264ebe6a8115028aa15c81af4fd98f1.tar.gz
binutils-b57264372264ebe6a8115028aa15c81af4fd98f1.tar.bz2
In gdb.threads/pthreads.c, handle pthread_attr_setscope ENOTSUP
On Cygwin, I see: (gdb) PASS: gdb.threads/pthreads.exp: break thread1 continue Continuing. pthread_attr_setscope 1: Not supported (134) [Thread 3732.0x265c exited with code 1] [Thread 3732.0x2834 exited with code 1] [Thread 3732.0x2690 exited with code 1] Program terminated with signal SIGHUP, Hangup. The program no longer exists. (gdb) FAIL: gdb.threads/pthreads.exp: Continue to creation of first thread ... and then a set of cascading failures. Fix this by treating ENOTSUP the same way as if PTHREAD_SCOPE_SYSTEM were not defined. I.e., ignore ENOTSUP errors, and proceed with testing. Approved-By: Tom Tromey <tom@tromey.com> Change-Id: Iea68ff8b9937570726154f36610c48ef96101871
-rw-r--r--gdb/testsuite/gdb.threads/pthreads.c3
1 files changed, 2 insertions, 1 deletions
diff --git a/gdb/testsuite/gdb.threads/pthreads.c b/gdb/testsuite/gdb.threads/pthreads.c
index 547bf0f..4b8b283 100644
--- a/gdb/testsuite/gdb.threads/pthreads.c
+++ b/gdb/testsuite/gdb.threads/pthreads.c
@@ -24,6 +24,7 @@
#include <pthread.h>
#include <unistd.h>
#include <string.h>
+#include <errno.h>
static int verbose = 0;
@@ -135,7 +136,7 @@ main (int argc, char **argv)
#ifdef PTHREAD_SCOPE_SYSTEM
res = pthread_attr_setscope (&attr, PTHREAD_SCOPE_SYSTEM);
- if (res != 0)
+ if (res != 0 && res != ENOTSUP)
{
print_error ("pthread_attr_setscope 1", res);
exit (1);