diff options
| author | Pedro Alves <pedro@palves.net> | 2023-09-15 19:43:55 +0100 |
|---|---|---|
| committer | Pedro Alves <pedro@palves.net> | 2023-09-27 15:28:39 +0100 |
| commit | f3e4716cc534f9521bd97abc400d8e8f0e73ea6a (patch) | |
| tree | 33e140f7d30ef54e63703cbd39d5c0cd1249bab2 /binutils/configure | |
| parent | ed11fb37b3f3de0f9cf056c9fce76dc7a3cc359d (diff) | |
| download | binutils-f3e4716cc534f9521bd97abc400d8e8f0e73ea6a.zip binutils-f3e4716cc534f9521bd97abc400d8e8f0e73ea6a.tar.gz binutils-f3e4716cc534f9521bd97abc400d8e8f0e73ea6a.tar.bz2 | |
Fix gdb.threads/pthreads.exp error handling/printing
On Cygwin, I noticed:
(gdb) PASS: gdb.threads/pthreads.exp: break thread1
continue
Continuing.
pthread_attr_setscope 1: No error
[Thread 8732.0x28f8 exited with code 1]
[Thread 8732.0xb50 exited with code 1]
[Thread 8732.0x17f8 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
Note "No error" in "pthread_attr_setscope 1: No error". That is a bug
in the test. It is using perror, but that prints errno, while the
pthread functions return the error directly. Fix all cases of the
same problem, by adding a new print_error function and using it.
We now get:
...
pthread_attr_setscope 1: Not supported (134)
...
Approved-By: Tom Tromey <tom@tromey.com>
Change-Id: I972ebc931b157bc0f9084e6ecd8916a5e39238f5
Diffstat (limited to 'binutils/configure')
0 files changed, 0 insertions, 0 deletions