Caveats about System.Diagnostics.StackTrace

Aufrufende Routinen rausbekommen ? | hilpers

Aufrufende Routinen rausbekommen ? | hilpers — Tue, 20 Jan 2009 19:18:03 GMT

PingBack from http://www.hilpers.com/875636-aufrufende-routinen-rausbekommen

Copyright Revewals » Mike Stall’s .NET Debugging Blog : Caveats about System.Diagnostics …

Wed, 02 Apr 2008 13:15:06 GMT

PingBack from http://copyrightrenewalsblog.info/mike-stalls-net-debugging-blog-caveats-about-systemdiagnostics/

MSDN Blog Postings » Why debugging breaks in optimized (production) builds.

MSDN Blog Postings » Why debugging breaks in optimized (production) builds. — Fri, 05 Oct 2007 20:37:30 GMT

PingBack from http://msdnrss.thecoderblogs.com/2007/10/05/why-debugging-breaks-in-optimized-production-builds/

Why debugging breaks in optimized (production) builds.

Mike Stall's .NET Debugging Blog — Fri, 05 Oct 2007 19:09:43 GMT

You may have noticed that debugging optimized builds (eg, what you commonly get when you attach to a

blog.iridescence.no : Getting the Current Stack Trace

blog.iridescence.no : Getting the Current Stack Trace — Wed, 11 Apr 2007 00:41:42 GMT

PingBack from http://blog.iridescence.no/Posts/GettingtheCurrentStackTrace.aspx

You can't get a mixed-mode callstack from inprocess.

Mike Stall's .NET Debugging Blog — Wed, 10 Aug 2005 08:21:56 GMT

You can't get a full-mixed (both managed+ native) stack of a thread within your own process. You can...

re: Caveats about System.Diagnostics.StackTrace

Qflash — Tue, 17 May 2005 13:09:39 GMT

RePost:
http://www.yeyan.cn/Programming/CaveatsSystemDiagnosticsStackTrace.aspx

re: Caveats about System.Diagnostics.StackTrace

Mike Stall — Thu, 31 Mar 2005 01:01:00 GMT

Jason - your observations are right on. The stack trace is naive with respect to cross thread calls. It just traces the current thread and stops.

FYI, VS can show cross-thread stack traces because it does a extra work under the covers:
- getting stack trace from all threads of interest
- tracking cross-thread calls in the stack trace
- stitching the stacks back together based off the cross-thread calls into a single unified stack.

One approach would be to have a wrapper around the Queue function which grabs a stack trace and stores it in your message.

re: Caveats about System.Diagnostics.StackTrace

Jason Coyne — Thu, 31 Mar 2005 00:18:00 GMT

I am trying to use the StackTrace class to get my current stack trace for some logging. Everything is working fine, except when I am using threading (specifically WaitCallBack and ThreadPool.QueueUserWorkItem)

When I try to walk the stack from a location that has been called via QueueUserWorkItem, the stack stops at the point where the thread was launched. Is there a way to walk back further into the parent thread's stack (at the time that my own thread was created, not the current state)

Thanks, Jason.

re: Caveats about System.Diagnostics.StackTrace

mihailik — Thu, 24 Mar 2005 13:23:00 GMT

Yeah, I found that little note in doc.

I think, it must be stated with more tension in documentation — many people can skip this small note and fall into misunderstanding.

Thank you for important information, Mike.