[Mono-bugs] [Bug 37411][Maj] New - mono crashes with unknown type error

[bugzilla-daemon@rocky.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 mathpup@mylinuxisp.com.

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

--- shadow/37411	Thu Jan 30 02:50:03 2003
+++ shadow/37411.tmp.8475	Thu Jan 30 02:50:03 2003
@@ -0,0 +1,61 @@
+Bug#: 37411
+Product: Mono/Runtime
+Version: unspecified
+OS: 
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Major
+Component: misc
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: mathpup@mylinuxisp.com               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: mono crashes with unknown type error
+
+Description of Problem: 
+ 
+When running the attached program, mono aborts with the error 
+ 
+** (static2.exe:19658): WARNING **: unknown type 14 
+ 
+** ERROR **: file helpers.c: line 492 (mono_map_call_type): should not be reached 
+aborting... 
+ 
+ 
+Steps to reproduce the problem: 
+1.  mcs static2.cs 
+2.  mono static2.exe 
+ 
+ 
+Actual Results: 
+ 
+** (static2.exe:19658): WARNING **: unknown type 14 
+ 
+** ERROR **: file helpers.c: line 492 (mono_map_call_type): should not be reached 
+aborting... 
+ 
+ 
+Expected Results: 
+ 
+Prints "A" 
+ 
+ 
+How often does this happen?  
+ 
+Always 
+ 
+Additional Information: 
+ 
+Rotor's csc  and mcs compile the program without complaint. Rotor's runtime is not 
+able to run mcs's output (probably a Rotor bug), but Rotor does run the output of 
+csc correctly. 
+ 
+In addition, I noticed that the problem only occurs when the array has at least two 
+dimensions. If I alter the program to use one-dimensional arrays everywhere, the 
+problem does not occur. On the other hand, changing from two to three dimensions 
+still results in the same crash. I suspect that this might be related to the fact that 
+one-dimensional arrays ("vectors") are treated differently in the CLI.