[Mono-bugs] [Bug 60766][Maj] Changed - MOD_MONO & XSP both have fatal errors on OS X
bugzilla-daemon@bugzilla.ximian.com
bugzilla-daemon@bugzilla.ximian.com
Tue, 6 Jul 2004 14:44:12 -0400 (EDT)
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 dru@satori-assoc.com.
http://bugzilla.ximian.com/show_bug.cgi?id=60766
--- shadow/60766 2004-07-05 09:34:21.000000000 -0400
+++ shadow/60766.tmp.15638 2004-07-06 14:44:12.000000000 -0400
@@ -76,6 +76,25 @@
------- Additional Comments From dru@satori-assoc.com 2004-07-04 13:02 -------
further digging, this is the appdomain bug, and can be reproduced using the
appdomain.cs test in mono/tests/appdomain.cs.
------- Additional Comments From lupus@ximian.com 2004-07-05 09:34 -------
*** Bug 60927 has been marked as a duplicate of this bug. ***
+
+------- Additional Comments From dru@satori-assoc.com 2004-07-06 14:44 -------
+More digging. It appears that the tramp-ppc is not calling the mono_domain_get() with
+the code to be JIT'ed. comparing Tramp-x86.c and tramp-ppc.c shows that the x86
+tramp tries to resolve the domain from the code to jitted, while the -ppc version does
+not.
+
+I'm now officially in over my head :-), but it appears that a similar check structure in
+tramp-ppc to make sure that the secondary domain reference is created would resolve
+this issue:
+
+ } else if ((code [1] == 0xe8)) {
+ MonoJitInfo *ji =
+ mono_jit_info_table_find (mono_domain_get (), code);
+ MonoJitInfo *target_ji =
+ mono_jit_info_table_find (mono_domain_get (), addr);
+
+though I'm unclear on the meaning of 0xe8 in that context.
+