[Mono-bugs] [Bug 74921][Maj] Changed - The runtime doesn't work correctly when compiled with gcc-4.0

[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 bmaurer at users.sf.net.

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

--- shadow/74921	2005-06-14 00:29:05.000000000 -0400
+++ shadow/74921.tmp.2539	2005-06-14 09:16:15.000000000 -0400
@@ -105,6 +105,55 @@
 ------- Additional Comments From bmaurer at users.sf.net  2005-06-14 00:29 -------
 Well, given that FC4 is released and has gcc 4, and that suse 10 is
 coming out in 5-6 months, as is ubuntu breezy, both with gcc 4 and
 native mono support it would be good to fix this sooner-rather-than-later.
 
 Am trying to enlist them help of some gcc people...
+
+------- Additional Comments From bmaurer at users.sf.net  2005-06-14 09:16 -------
+From: 	Marcus Meissner <meissner at suse.de>
+To: 	research at suse.de, bmaurer at ximian.com
+Subject: 	Re: [Research] Mono and GCC 4.0
+Date: 	Tue, 14 Jun 2005 14:18:36 +0200  (08:18 EDT)
+
+On Mon, Jun 13, 2005 at 04:46:32PM -0400, Ben Maurer wrote:
+> Hey guys,
+> 
+> We are having an issue with Mono and the latest GCC 4.
+> 
+> Try downloading this tarball:
+> 
+> http://primates.ximian.com/~bmaurer/mono-1.1.8.tar.gz
+> 
+> run configure; make; make check. It will segfault during the basic.exe
+> tests. I've only seen this on distros using gcc4. I know it happens on
+> x86, haven't tried other archs.
+> 
+> Do any gcc experts here have ideas?
+> 
+
+cd mono/mini/
+
+strace -if ./mono --optimized=shared basic.exe
+
+gives this strace snippet:
+[08108c04] --- SIGSEGV (Segmentation fault) @ 0 (0) ---
+[0811e59d] --- SIGSEGV (Segmentation fault) @ 0 (0) ---
+
+This section is in the brk() section, which is at this time
+not mapped executable.
+
+It must be mapped executable to be able to execute code.
+
+There is one mprotect call affecting the brk() section:
+[401b7ea4] mprotect(0x081b8000, 4096, PROT_READ|PROT_WRITE|PROT_EXEC) = 0
+[401b7ea4] mprotect(0x081b8000, 4096, PROT_READ|PROT_WRITE|PROT_EXEC) = 0
+
+But this does not contain the above instructions.
+
+At least this is my assumption.
+
+Ciao, Marcus
+---------
+
+
+Any comments here?