[Mono-bugs] [Bug 74937][Blo] Changed - 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.16743	2005-05-13 11:56:02.000000000 -0400
@@ -1,14 +1,14 @@
 Bug#: 74937
 Product: Mono: Runtime
 Version: 1.1
-OS: 
+OS: unknown
 OS Details: 
 Status: NEW   
 Resolution: 
-Severity: 
+Severity: Unknown
 Priority: Blocker
 Component: misc
 AssignedTo: martin@ximian.com                            
 ReportedBy: michael@ximian.com               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
@@ -45,6 +45,11 @@
 (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 ?
+
+------- Additional Comments From michael@ximian.com  2005-05-13 11:56 -------
+Prolly worth pointing out that the type itself is not Null: when
+printed with ToString it prints the type of the type it is
+representing correctly.