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=81685 --- shadow/81685 2007-05-24 06:31:13.000000000 -0400 +++ shadow/81685.tmp.3305 2007-05-24 11:48:31.000000000 -0400 @@ -159,6 +159,14 @@ ------- Additional Comments From [EMAIL PROTECTED] 2007-05-24 06:31 ------- Jim likely talked about stack overflow in unmanaged code and as I said above, it's hard to recover in that case, the only option may be to abort. The issue is different with managed code overflows, which we need to handle (and the MS implementation handles as well). + +------- Additional Comments From [EMAIL PROTECTED] 2007-05-24 11:48 ------- +We were talking specifically about managed code not about interactions +with unmanaged code (which would make things even worse). + +One of the points is finalizers: there is no way you can guarantee +proper unwinding if the finalizers can potentially cause another stack +overflow (as Robert example shows). _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
