[Mono-bugs] [Bug 77028][Min] Changed - mono build process segfaults on powerpc

[bugzilla-daemon at bugzilla.ximian.com]

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 slomo at ubuntu.com.

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

--- shadow/77028	2006-07-05 04:58:57.000000000 -0400
+++ shadow/77028.tmp.28469	2006-07-06 18:00:13.000000000 -0400
@@ -1,13 +1,13 @@
 Bug#: 77028
 Product: Mono: Runtime
 Version: 1.1
 OS: unknown
 OS Details: Ubuntu
-Status: REOPENED   
-Resolution: 
+Status: RESOLVED   
+Resolution: FIXED
 Severity: Unknown
 Priority: Minor
 Component: misc
 AssignedTo: lupus at ximian.com                            
 ReportedBy: slomo at ubuntu.com               
 QAContact: mono-bugs at ximian.com
@@ -471,6 +471,35 @@
 http://librarian.launchpad.net/3205764/buildlog_ubuntu-edgy-powerpc.beagle_0.2.7-0ubuntu2_FAILEDTOBUILD.txt.gz
 
 I can't provide more debug informations as I don't have direct access
 to  such a machine :(
 
 Johannes, can you reproduce this?
+
+------- Additional Comments From slomo at ubuntu.com  2006-07-06 18:00 -------
+Ok, this is definetly another problem that also happens on PPC32. I
+filed a new bug for it: bug #78782.
+
+Also Johannes noted the following which was helpful for getting useful
+output for the new bug:
+
+[talking about mono/ppc running on ppc64, with the fix from svn 61756
+applied, still segfaults occasionally]
+
+Looking at the code again, I notice that the debugger function isn't
+fixed:
+
+mono_debugger_create_notification_function:
+
+        ptr = buf = g_malloc0 (16);
+
+which is then used as code. But I doubt this one is causing the
+problem here.
+
+Also, in mono_arch_emit_prolog, we have another instance where code is
+malloc'ed:
+
+        code = cfg->native_code = g_malloc (cfg->code_size);
+
+That could very well be causing this issue again.
+
+johannes