[Mono-bugs] [Bug 35280][Wis] New - The "checked" C# keyword halts the execution of both MONO and MINT

[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 pluto@tipic.com.

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

--- shadow/35280	Sun Dec  8 12:52:38 2002
+++ shadow/35280.tmp.2383	Sun Dec  8 12:52:38 2002
@@ -0,0 +1,84 @@
+Bug#: 35280
+Product: Mono/Runtime
+Version: unspecified
+OS: 
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Wishlist
+Component: misc
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: pluto@tipic.com               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: The "checked" C# keyword halts the execution of both MONO and MINT
+
+Please fill in this template when reporting a bug, unless you know what 
+you are doing.
+Description of Problem:
+
+The "checked" C# keyword seems to halt both the execution of MINT and MONO.
+
+Steps to reproduce the problem:
+Just compile and run the following sub
+
+void func() {
+int local1;
+float local2;
+
+local2 = 20000 * Microsoft.VisualBasic.VBMath.Rnd();
+local1 = checked((int) Math.Round((double) (float) (float)
+                 Environment.TickCount + local2));
+}
+
+Actual Results:
+MINT: 
+$ mint  C:\\temp\\ConsoleApplication2\\bin\\Debug\\ConsoleApplication2.exe
+Execution aborted in method: Class1::Main
+Line=3386 IP=0x0022, Aborted execution
+0x0022 b7
+        [1] 1 0x30000000 104895756.00000
+MONO: 
+$ mono  C:\\temp\\ConsoleApplication2\\bin\\Debug\\ConsoleApplication2.exe
+
+C:\temp\ConsoleApplication2\bin\Debug\ConsoleApplication2.exe (pid:2296): 
+** WAR
+NING **: tree does not match in 00 ConsoleApplication2.Class1:Main (string
+[]): 0
+x0023
+ (STIND_I4 ADDR_L[ESI|2] (CONV_OVF_I4 (LDIND_R8 ADDR_L[9])))
+
+        (STIND_I4 ADDR_L[ESI|5] NEWOBJ_SPEC)
+        (CALL_VOID (LDIND_I4 ADDR_L[ESI|5]) ADDR_G)
+        (STIND_I4 ADDR_L[EBX|1] (LDIND_I4 ADDR_L[ESI|5]))
+        (STIND_R8 ADDR_L[6] (CALL_R8 (LDIND_I4 ADDR_G) VFUNC_ADDR))
+        (STIND_R4 ADDR_G (CONV_R4 (LDIND_R8 ADDR_L[6])))
+        (STIND_R8 ADDR_L[7] (MUL CONST_R4 (LDIND_R4 ADDR_G)))
+        (STIND_R4 ADDR_L[3] (LDIND_R8 ADDR_L[7]))
+        (STIND_I4 ADDR_L[ESI|8] (CALL_I4 NOP ADDR_G))
+        (ARG_R8 (ADD (CONV_R8 (CONV_R4 (CONV_R4 (LDIND_I4 ADDR_L
+[ESI|8])))) (CON
+V_R8 (LDIND_R4 ADDR_L[3]))))
+        (STIND_R8 ADDR_L[9] (CALL_R8 NOP ADDR_G))
+        (STIND_I4 ADDR_L[ESI|2] (CONV_OVF_I4 (LDIND_R8 ADDR_L[9])))
+        (ARG_I4 (LDIND_I4 ADDR_L[4]))
+        (CALL_VOID (LDIND_I4 ADDR_L[EBX|1]) ADDR_G)
+        RET_VOID
+
+abnormal program termination
+
+Expected Results:
+Just prints nothing and does few conversions
+
+
+How often does this happen? 
+Always
+
+Additional Information:
+Every VB.NET programs usues, by default, checks on integer conversion: so, 
+while this construct is not very common in c#, it happens very often in 
+VB.NET programs (this check is enabled -by default- for every program, you 
+have to explicitly disable it)