[Mono-bugs] [Bug 78767][Nor] Changed - can't load libmono as a module

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Wed Aug 9 09:32:07 EDT 2006


Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by vargaz at gmail.com.

http://bugzilla.ximian.com/show_bug.cgi?id=78767

--- shadow/78767	2006-08-09 07:06:53.000000000 -0400
+++ shadow/78767.tmp.16117	2006-08-09 09:32:07.000000000 -0400
@@ -262,6 +262,20 @@
 when it's not actually used ].
 
 Wrt. renaming libmono - to libmono-module: if that works for you, I'm
 fine with it [ any solution is good I guess ;-]. OTOH - surely having
 a statically linked version to 'mono' will make 'mono' even smaller,
 more efficent & faster to start.
+
+------- Additional Comments From vargaz at gmail.com  2006-08-09 09:32 -------
+The 'initial-exec' TLS model for a shared library is clearly wrong,
+both according to the docs, and according to experience.
+
+Disabling the VAR_OFFSET stuff in the PIC case slows down the shared
+library case a bit, but its not very tragic, also, it can be enabled
+again if somebody figures out why the original one does not work.
+(Probably because it cannot be made to work, i.e. it is not possible to
+determine the TLS offset used by a TLS variable in a shared library
+during compile time). What would be useful is some kind of libc call,
+which given the reference to a TLS reference, would return the TLS offset.
+
+Anyway, I will check in this change.


More information about the mono-bugs mailing list