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=77008 --- shadow/77008 2005-12-15 16:04:26.000000000 -0500 +++ shadow/77008.tmp.27223 2005-12-15 16:07:12.000000000 -0500 @@ -3,13 +3,13 @@ Version: 1.1 OS: unknown OS Details: Status: NEW Resolution: Severity: Unknown -Priority: Normal +Priority: Wishlist Component: C# AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] QAContact: [EMAIL PROTECTED] TargetMilestone: --- URL: @@ -85,6 +85,23 @@ I shouldn't have to tell you that a NullReferenceException should NEVER occur in production code. NEVER. It is a sign of sloppy coding-- it means that a routine is not checking its arguments or that the programmer did not expect a null return from a method or property. If a debugger existed for Mono, I'd be glad to track down the error myself. + +------- Additional Comments From [EMAIL PROTECTED] 2005-12-15 16:07 ------- +It's hard to track this kind of thing without source code. The best +way is if you can isolate a smaller test case which you can share. The +stack trace can help you narrow your search: + +in <0x00036> Mono.CSharp.Enum:Emit () + +It is happening while an enum is being emitted + +in <0x0009c> Mono.CSharp.Attributes:Emit (Mono.CSharp.EmitContext ec, +Mono.CSharp.Attributable ias) + +The enum (or maybe one of it's values) has an attribute. These two +things should help you narrow something down. You could also recompile +MCS with a Console.WriteLine in Mono.CSharp.Enum:Emit () that printed +Location. This would tell you exactly which enum was causing the problem. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
