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=79717 --- shadow/79717 2006-10-22 14:02:57.000000000 -0400 +++ shadow/79717.tmp.27723 2006-10-23 09:25:58.000000000 -0400 @@ -87,6 +87,11 @@ ------- Additional Comments From [EMAIL PROTECTED] 2006-10-22 14:02 ------- Yep, it seems like the stacktrace should contain all methods from the AsyncCallback routine and beyond. It doesn't matter much to me to see the rest of the internal functions, maybe other people care more? I guess I can't see why they would or how they could rely on the internal .net execution flow however. + +------- Additional Comments From [EMAIL PROTECTED] 2006-10-23 09:25 ------- +This is caused by frame pointer elimination since the exception code +uses MONO_CONTEXT_GET_BP (&ctx) < jit_tls->end_of_stack to detect +the end of the stack. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
