[Mono-bugs] [Bug 76996][Nor] Changed - Inconsistent behaviour on PPC when throwing an exception in a finally block

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Wed Dec 14 16:21:07 EST 2005


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 robertj at gmx.net.

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

--- shadow/76996	2005-12-14 13:16:46.000000000 -0500
+++ shadow/76996.tmp.3828	2005-12-14 16:21:07.000000000 -0500
@@ -1,23 +1,23 @@
 Bug#: 76996
 Product: Mono: Runtime
 Version: 1.1
-OS: 
+OS: unknown
 OS Details: Ubuntu
 Status: NEW   
 Resolution: 
-Severity: 
-Priority: Major
+Severity: Unknown
+Priority: Normal
 Component: misc
 AssignedTo: mono-bugs at ximian.com                            
 ReportedBy: slomo at ubuntu.com               
 QAContact: mono-bugs at ximian.com
 TargetMilestone: ---
 URL: 
 Cc: 
-Summary: Inconsistent behaviour on PPC and x86 when throwing an exception in a finally block
+Summary: Inconsistent behaviour on PPC when throwing an exception in a finally block
 
 Hi,
 the following testcase produces two different results on PPC and x86 when
 using the same mono version (1.1.10.1), etc. On PPC it crashes because of
 an unhandled Exception (the bar one, the other isn't reported at all), on
 x86 it writes the bar-Exception on the console and continues to work but
@@ -74,6 +74,13 @@
 			System.Console.WriteLine(e);
 		}
 		System.Console.WriteLine("ok");
 	}
 
 }
+
+------- Additional Comments From robertj at gmx.net  2005-12-14 16:21 -------
+"foo" cannot be reported, because the outer catch block
+never sees this exception. This is by design.
+
+Removed "x86" from the subject and changed the prio to "normal".
+


More information about the mono-bugs mailing list