[Mono-bugs] [Bug 74937][Blo] New - custom type failure ..

[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 michael@ximian.com.

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

--- shadow/74937	2005-05-13 11:52:03.000000000 -0400
+++ shadow/74937.tmp.16727	2005-05-13 11:52:03.000000000 -0400
@@ -0,0 +1,50 @@
+Bug#: 74937
+Product: Mono: Runtime
+Version: 1.1
+OS: 
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Blocker
+Component: misc
+AssignedTo: martin@ximian.com                            
+ReportedBy: michael@ximian.com               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: custom type failure ..
+
+So - we have a custom Type derived from 'Type' 'PolymorphicType' the code
+is here:
+http://go-oo.org/lxr/source/udk/cli_ure/source/basetypes/uno/PolymorphicType.cs
+
+Everything goes smoothly, until we create a polymorphic type:
+
+            result = uno.PolymorphicType.GetType(result, unoName);
+
+and then shortly afterwards do:
+
+typeof(unoidl.com.sun.star.uno.Exception).IsAssignableFrom(result);
+
+at which point we get a SEGV:
+
+Program received signal SIGSEGV, Segmentation fault.
+[Switching to Thread 1075952576 (LWP 8859)]
+mono_class_from_mono_type (type=0x0) at class.c:2621
+2621            switch (type->type) {
+(gdb) bt
+#0  mono_class_from_mono_type (type=0x0) at class.c:2621
+#1  0x080ccd5b in ves_icall_type_is_assignable_from (type=0x81f4730,
+c=0x838fe88) at icall.c:1177
+
+(gdb) up
+#1  0x080ccd5b in ves_icall_type_is_assignable_from (type=0x81f4730,
+c=0x838fe88) at icall.c:1177
+(gdb) p *c
+$2 = {object = {vtable = 0x83c6d90, synchronisation = 0x0}, type = 0x0}
+
+Any ideas ? of course - it could be something totally unrelated :-) is it
+possible that 99.9% of types are constructed by Mono & => have this sort of
+thing setup properly by the time it gets here ?