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 [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=82012 --- shadow/82012 2007-07-09 04:29:41.000000000 -0400 +++ shadow/82012.tmp.12311 2007-07-09 04:39:19.000000000 -0400 @@ -111,6 +111,16 @@ end that the change that "broke" mod_mono is the corlib version update. I suggest you bootstrap your mono installation from scratch (mcs, mono, xsp, mod_mono), purging your gac before that. I've just done that and mod_mono suddenly works. It is likely that the old corlib is lurking somewhere around stopping mod-mono-server from working. Please let me know if it works for you after bootstrapping. + +------- Additional Comments From [EMAIL PROTECTED] 2007-07-09 04:39 ------- +The likely cause of the problem is that there were breaking changes +introduced into the corlib interfaces in one revision, but the corlib +version number was bumped a bit after that, in another revision. This +causes the situation where the incompatible corlib is treated as +correct but it does contain the breaking changes which, if used by +application(s) compiled with the older corlib, can cause memory +corruption in certain execution paths. For that reason the bootstrap +is necessary. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
