strerror is now thread safe (#8648)

Before glibc 2.32, `strerror`() is not MT-Safe.
(from man strerror on Ubuntu 26.04).

 glibc 2.32 was released on 2020-08-05 and glibc 2.43 on 2026-01-24
(from https://sourceware.org/glibc/wiki/Glibc%20Timeline)

This patch stops the `threadsafety.py` addon from warning about
`strerror()`.

`strerror` was used in `test/cli/other_test.py` to test
`threadsafety.py` so we also patch that to use a different thread-unsafe
function.

Author: andrew-aitchison

addons/threadsafety.py

@@ -91,7 +91,6 @@
     'race:stdin',
     'race:stdout',
     'race:streams',
-    'race:strerror',
     'race:strsignal',
     'race:strtok',
     'race:tmbuf',
@@ -261,7 +260,6 @@
     'siginterrupt',
     'sleep',
     'srand48',
-    'strerror',
     'strsignal',
     'strtok',
     'tmpnam',

test/cli/other_test.py

@@ -482,9 +482,9 @@ def test_addon_threadsafety(tmpdir):
     test_file = os.path.join(tmpdir, 'test.cpp')
     with open(test_file, 'wt') as f:
         f.write("""
-extern const char* f()
+extern void f()
 {
-    return strerror(1);
+    elf_fill(1);
 }
         """)
 
@@ -496,7 +496,7 @@ def test_addon_threadsafety(tmpdir):
     assert lines == [
         'Checking {} ...'.format(test_file)
     ]
-    assert stderr == '{}:4:12: warning: strerror is MT-unsafe [threadsafety-unsafe-call]\n'.format(test_file)
+    assert stderr == '{}:4:5: warning: elf_fill is MT-unsafe [threadsafety-unsafe-call]\n'.format(test_file)
 
 
 def test_addon_naming(tmpdir):