[Mono-bugs] [Bug 59649][Blo] Changed - New libgc breaks Mono on Windows (XP SP1)
bugzilla-daemon@bugzilla.ximian.com
bugzilla-daemon@bugzilla.ximian.com
Mon, 7 Jun 2004 02:24:15 -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 gert.driesen@pandora.be.
http://bugzilla.ximian.com/show_bug.cgi?id=59649
--- shadow/59649 2004-06-07 01:43:10.000000000 -0400
+++ shadow/59649.tmp.5762 2004-06-07 02:24:15.000000000 -0400
@@ -127,6 +127,27 @@
------- Additional Comments From miguel@ximian.com 2004-06-07 01:03 -------
Am CCing Gonzalo and Sebastien who run Mono on Windows.
------- Additional Comments From gonzalo@ximian.com 2004-06-07 01:43 -------
I can run mono on windows and I use that libgc, which, btw, is the one
shipped with the installer.
+
+------- Additional Comments From gert.driesen@pandora.be 2004-06-07 02:24 -------
+I just verified that I only get the issue on Windows XP (SP1). Using
+the exact same cygwin environment on Windows 2003 works fine.
+
+On Windows XP SP1, I only have this problem when using both the
+gc.dll and the headers from the new libgc release. Everything works
+fine if I use the new gc.dll, but the old headers files.
+
+I also have no problems using a Mono runtime built on W2K3 (with the
+new libgc) on Windows XP (SP1).
+
+If I recall correctly, everything worked fine prior to installing
+Windows XP SP1, so it might be due to extra (memory ?) protection in
+SP1 or so (but why would it only surface when using the new header
+files?).
+
+I do have a workaround (meaning using the old header files), so I
+don't mind lowering the priority of this issue...
+
+Are any of you using XP SP1 too ?