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=79452 --- shadow/79452 2006-09-22 05:29:45.000000000 -0400 +++ shadow/79452.tmp.25447 2006-09-22 08:30:34.000000000 -0400 @@ -93,6 +93,26 @@ ------- Additional Comments From [EMAIL PROTECTED] 2006-09-22 05:29 ------- We would fix it but don't know how to. For example, under MS, if I print the stack trace in ReThrowFooBar (), it doesn't include the Main method, but when I print it out in Main, it does. So we _do_ preserve the stack trace, while MS changes it during a rethrow. + +------- Additional Comments From [EMAIL PROTECTED] 2006-09-22 08:30 ------- +"For example, under MS, +if I print the stack trace in ReThrowFooBar (), it doesn't include the +Main method, but when I print it out in Main, it does." + +That's ok. An exception stack trace should include stack trace +information upto the method which handles it. + +"So we _do_ preserve the stack trace, while MS changes it during a +rethrow." + +Interesting. + +Would it be possible to append stack trace information during a +rethrow to match the clr behavior then? + +If it does not seem doable, would someone be kind enough to provide +some pointers on why and where to look in the source code to try to +come up with a patch? _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
