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=77596 --- shadow/77596 2007-07-20 10:23:17.000000000 -0400 +++ shadow/77596.tmp.2434 2007-07-20 10:26:56.000000000 -0400 @@ -227,6 +227,34 @@ ------- Additional Comments From [EMAIL PROTECTED] 2007-07-20 10:23 ------- On further thought, that isn't the correct fix. It's a quick bandage which should solve the SEGV. But, the semantics require a different fix -- which I hope will also solve some other issues with MonoGenericInst. + +------- Additional Comments From [EMAIL PROTECTED] 2007-07-20 10:26 ------- +I am trying patch moved above the + +if (type->type == MONO_TYPE_GENERICINST) { + +line, since that line is where I crash when trying to use type. + + +Also, I haven't verified yet but I think this can arise outside of +System.System.Xml. For example. + +A.dll +class A<T> + +B.Dll +class B<T> + +C.exe +{ +A<B<int>> one_way; +B<A<int>> other_way; +} + +No matter what (before the patch), on shutdown image A or B will be +unloaded before the other leading to a type from one image referencing +a type from a freed mempool. + _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
