summaryrefslogtreecommitdiff
path: root/faq
diff options
context:
space:
mode:
authorThomas Schwinge <thomas@codesourcery.com>2013-09-26 15:40:02 +0200
committerThomas Schwinge <thomas@codesourcery.com>2013-09-26 15:40:02 +0200
commitb754e34876f46a227be63c08d02e13817e54e409 (patch)
tree3c6ee62fe978b61c8ba86db7efe9f4355b09602f /faq
parent36c6bdaf4ef0b48dc8b1aa2b4373c48d25b3594d (diff)
parentad6980f0500d745c8861c29c4015039743620bad (diff)
Merge commit 'ad6980f0500d745c8861c29c4015039743620bad'
Diffstat (limited to 'faq')
-rw-r--r--faq/libpthread_dlopen.mdwn (renamed from faq/libpthread_plugin.mdwn)12
1 files changed, 8 insertions, 4 deletions
diff --git a/faq/libpthread_plugin.mdwn b/faq/libpthread_dlopen.mdwn
index bcbe9571..5fb77767 100644
--- a/faq/libpthread_plugin.mdwn
+++ b/faq/libpthread_dlopen.mdwn
@@ -10,12 +10,16 @@ License|/fdl]]."]]"""]]
[[!tag faq/open_issues]]
-[[!meta title="Getting Assertion `__pthread_threads' failed."]]
+[[!meta title="Assertion `__pthread_threads' failed"]]
-Some applications don't link against libpthread, but load plugins which do link against libpthread. This means unexpectedly switch from mono-thread to multi-thread. This is not supported yet, thus the following error:
+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:
./pthread/../sysdeps/generic/pt-mutex-timedlock.c:70: __pthread_mutex_timedlock_internal: Assertion `__pthread_threads' failed.
-This can be worked around by using
+This can be worked around by explicitly pre-loading libpthread, for example:
-export LD_PRELOAD=/lib/i386-gnu/libpthread.so.0.3
+ $ LD_PRELOAD=/lib/i386-gnu/libpthread.so.0.3 [application]