[Mono-bugs] [Bug 78782][Blo] Changed - Segfault on PPC when using a libgcc_s/libpthread compiled with SSP

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Fri Jul 7 06:33:22 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 johannes at sipsolutions.net.


--- shadow/78782	2006-07-07 06:21:29.000000000 -0400
+++ shadow/78782.tmp.7430	2006-07-07 06:33:22.000000000 -0400
@@ -322,6 +322,15 @@
 end so we have 2 bugs here:
 1) the segfault somewhere in the unwinding code which is most probably
 caused by mono because it does weird things (maybe something with
 stack alignement? but this is only a wild guess)
 2) the segfault in the segfault handler of mono which can be fixed by
 using the codemanager instead of g_malloc() for some reason.
+------- Additional Comments From johannes at sipsolutions.net  2006-07-07 06:33 -------
+Except that (2) doesn't really make sense to me because the only
+difference should be that the code manager memory is executable while
+malloc()ed memory isn't ... but the G4 doesn't honour that anyway so
+all memory is executable when readable!
+Or maybe I'm missing something and there's another difference? Or
+something is overwriting the malloc()ed memory and not the other?

More information about the mono-bugs mailing list