In gdb.threads/pthreads.c, handle pthread_attr_setscope ENOTSUP
authorPedro Alves <pedro@palves.net>
Fri, 15 Sep 2023 19:06:37 +0000 (20:06 +0100)
committerPedro Alves <pedro@palves.net>
Wed, 27 Sep 2023 14:28:40 +0000 (15:28 +0100)
commitb57264372264ebe6a8115028aa15c81af4fd98f1
tree96d9e073cecc21a8916cb7f5be804cff7ea85886
parentf3e4716cc534f9521bd97abc400d8e8f0e73ea6a
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
gdb/testsuite/gdb.threads/pthreads.c