summaryrefslogtreecommitdiff
path: root/faq/libpthread_dlopen.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'faq/libpthread_dlopen.mdwn')
-rw-r--r--faq/libpthread_dlopen.mdwn12
1 files changed, 7 insertions, 5 deletions
diff --git a/faq/libpthread_dlopen.mdwn b/faq/libpthread_dlopen.mdwn
index 94d091a4..3b365fad 100644
--- a/faq/libpthread_dlopen.mdwn
+++ b/faq/libpthread_dlopen.mdwn
@@ -1,4 +1,5 @@
-[[!meta copyright="Copyright © 2013, 2014 Free Software Foundation, Inc."]]
+[[!meta copyright="Copyright © 2013, 2014, 2015 Free Software Foundation,
+Inc."]]
[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
id="license" text="Permission is granted to copy, distribute and/or modify this
@@ -14,12 +15,13 @@ License|/fdl]]."]]"""]]
Some applications don't themselves link against libpthread, but then load
plugins which do link against libpthread. This means internally switching from
-single-threading to multi-threading, which is [[not yet
-supported|open_issues/libpthread_dlopen]] by our [[/libpthread]], and results
-in errors such as:
+single-threading to multi-threading, which is only supported since libc0.3
+2.19-16~2. Previously, it would result in errors such as:
./pthread/../sysdeps/generic/pt-mutex-timedlock.c:70: __pthread_mutex_timedlock_internal: Assertion `__pthread_threads' failed.
-This can be worked around by making the application link against libpthread (i.e. not only the plugin, but also the main binary), or without recompiling by explicitly pre-loading libpthread, for example:
+This could be worked around by making the application link against libpthread (i.e. not only the plugin, but also the main binary), or without recompiling by explicitly pre-loading libpthread, for example:
$ LD_PRELOAD=/lib/i386-gnu/libpthread.so.0.3 [application]
+
+But it should now be gone, simply upgrade libc0.3.