[Mono-bugs] [Bug 79717][Nor] Changed - System.Diagnostics.StackTrace doesn't work properly inside of AsyncCallback routines

[bugzilla-daemon at bugzilla.ximian.com]

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 cmorgan at alum.wpi.edu.

http://bugzilla.ximian.com/show_bug.cgi?id=79717

--- shadow/79717	2006-10-22 06:07:21.000000000 -0400
+++ shadow/79717.tmp.6664	2006-10-22 12:54:57.000000000 -0400
@@ -66,6 +66,16 @@
 ------- Additional Comments From vargaz at gmail.com  2006-10-22 06:07 -------
 I think our StackTrace works just fine, its just that under MS.NET,
 the callback is invoked from managed code, while under mono, it is
 invoked from runtime code, so there are simply not frames to display
 under mono.
 
+
+------- Additional Comments From cmorgan at alum.wpi.edu  2006-10-22 12:54 -------
+Hmm.  I was trying to use this code to do a simple implementation of 
+tracing, where I'd throw in a call to trace.output() and it would 
+print the method name of StackTrace.GetFrame(1). I'm ok if it doesn't 
+give a complete stack trace but no stack trace makes it pretty 
+difficult to tell which routine we are tracing from. I don't claim to 
+know the technical details behind managed vs. runtime but it would be 
+nice if this could be worked around somehow to produce similar 
+stack output.