[Mono-bugs] [Bug 79400][Wis] New - Argument is out of range: index

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Thu Sep 14 16:14:33 EDT 2006

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 jve7gm at gmail.com.


--- shadow/79400	2006-09-14 16:14:33.000000000 -0400
+++ shadow/79400.tmp.25110	2006-09-14 16:14:33.000000000 -0400
@@ -0,0 +1,58 @@
+Bug#: 79400
+Product: Mono: Class Libraries
+Version: 1.0
+OS: All
+OS Details: Linux
+Status: NEW   
+Priority: Wishlist
+Component: Sys.Web
+AssignedTo: gonzalo at ximian.com                            
+ReportedBy: jve7gm at gmail.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+Summary: Argument is out of range: index
+Please fill in this template when reporting a bug, unless you know what 
+you are doing.
+Description of Problem:
+Very strange one this and unstable bug; i think i've narrowed it down to 
+these few lines; i get an index argument out of range exception when 
+trying to load a page from: shared/tools/mono/mono-
+Steps to reproduce the problem:
+1. See the attached sample.
+2. Basically add any type of <% %> tag to the head of the page, e.g. 
+before body actually begins. 
+3. Then ensure that the class the page Inherits statement, itself 
+inherits from another class in a different namespace which finally 
+inherits from page.
+Actual Results:
+Index Error in the generated BuildTree method, I added some more debug 
+info and the following was reported by ControlCollection.cs:
+System.ArgumentOutOfRangeException: Argument is out of range.
+Parameter name: count=2 index=2 owner=Bug02
+Expected Results:
+The page should load.
+How often does this happen? 
+Every time.
+Additional Information:
+I found that when removing the `keyword` line from the script, it solves 
+the issue.
+I also found that when getting the class to inherit directly from page it 
+also solves the issue.
+No idea how these are related, but both of them provide a workaround for 
+the problem.
+As close as I can get to the actual code which is generated is to remove 
+the ; from the keywords line in the head section to force a compiler 
+error so the generated source file can be seen - here all the generated 
+code seems to be in order appart from the missing ; in the BuildTree 

More information about the mono-bugs mailing list