[Mono-bugs] [Bug 79452][Wis] Changed - rethrow loses stack trace information
bugzilla-daemon at bugzilla.ximian.com
bugzilla-daemon at bugzilla.ximian.com
Fri Sep 22 05:29:45 EDT 2006
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 vargaz at gmail.com.
http://bugzilla.ximian.com/show_bug.cgi?id=79452
--- shadow/79452 2006-09-21 17:34:27.000000000 -0400
+++ shadow/79452.tmp.21042 2006-09-22 05:29:45.000000000 -0400
@@ -86,6 +86,13 @@
Would be really useful to get fixed even though it's hard.
Stacktraces are pretty important when developing code.
Especially in boo (and the derived unityscript), this means most of the duck typed code will
lose the important part of the stacktrace, so when you encounter an error, you have no clue
where it happened.
+
+------- Additional Comments From vargaz at gmail.com 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.
+
More information about the mono-bugs
mailing list