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:34:59.000000000 -0500 +++ shadow/77008.tmp.27754 2005-12-15 16:41:03.000000000 -0500 @@ -105,6 +105,33 @@ 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. ------- Additional Comments From [EMAIL PROTECTED] 2005-12-15 16:34 ------- Ugh, bugzilla midair collision caused priority to change + +------- Additional Comments From [EMAIL PROTECTED] 2005-12-15 16:41 ------- +Am inclined to think that if the project built /before/ you fixed a +bug in the class libraries that your fix on the class libraries is to +blame. + +Looking at the disassembly for offset 0x122 shows the following code: + +0x414febac cmp %eax,(%eax) +0x414febae call +0x414fea88:Mono.CSharp.DeclSpace.LookupType(System.String,Mono.CSharp.Location,System.Boolean) + +This code is in decl.cs: + + else if (Parent != null && Parent != RootContext.Tree.Types) + e = Parent.LookupType (name, loc, ignore_cs0104); + +So Parent is null, and as you can see it is being tested for that. + +There might be a number of explanations for why your code no longer +builds even after reinstalling. You might have something else in your +path, multiple installs or a combination of assorted problems. + +I would rebuild from a different user account that has not been +"customized" + + _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
