From 525c916632f6776353d05e34ef1788d921d1b19f Mon Sep 17 00:00:00 2001 From: Luca Bacci Date: Thu, 22 Jan 2026 14:30:07 +0100 Subject: [PATCH] gmodule/dl: Document thread-safety of dlerror in musl libc --- gmodule/gmodule-dl.c | 1 + 1 file changed, 1 insertion(+) diff --git a/gmodule/gmodule-dl.c b/gmodule/gmodule-dl.c index 5c1c7419b..ad5094d9f 100644 --- a/gmodule/gmodule-dl.c +++ b/gmodule/gmodule-dl.c @@ -96,6 +96,7 @@ * However, some libc implementations, such as glibc, implement dlerror() using * thread-local storage, so are thread-safe. As of early 2021: * - glibc is thread-safe: https://github.com/bminor/glibc/blob/HEAD/dlfcn/libc_dlerror_result.c + * - musl-libc is thread-safe since version 1.1.9 -- released in 2015: https://wiki.musl-libc.org/functional-differences-from-glibc.html#Thread-safety-of-%3Ccode%3Edlerror%3C/code%3E * - uclibc-ng is not thread-safe: https://cgit.uclibc-ng.org/cgi/cgit/uclibc-ng.git/tree/ldso/libdl/libdl.c?id=132decd2a043d0ccf799f42bf89f3ae0c11e95d5#n1075 * - Other libc implementations have not been checked, and no problems have * been reported with them in 10 years, so default to assuming that they