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-23 07:29:49.000000000 -0400 +++ shadow/81685.tmp.16043 2007-05-23 19:10:04.000000000 -0400 @@ -126,6 +126,23 @@ users. Having the checks only in the managed->unmanaged wrappers wouldn't reduce our performance in a significant way. + +------- Additional Comments From [EMAIL PROTECTED] 2007-05-23 19:10 ------- +I spoke to Jim Miller from the CLR group this week at Microsoft and he +pointed out that once a stack overflow is caught the only thing that +can be done is to shut down the process, he said that at that point +attempting to recover is not possible and the internals of the class +libraries and potential unmanaged frames is probably corrupt. + +The issue of finalization did come up, and this is part of the +"corrupted internal state" that happens during a stack overflow condition. + +I have not looked at what Silverlight does (someone mentioned during +the conversation that they just stop execution of the managed code and +return an error). + +Under these conditions it does not seem worth to implement, I thought +that Silvelright might be able to throw and have the exception be caught. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
