In my initial post about DoStackSnapshot , I touched on how and when your profiler can "fill in the holes" by walking the unmanaged parts of the stack itself. Doing this requires that your profiler have access to a register context at the top of the unmanaged...

Generally, corerror.h tells you all you need to know about what kinds of HRESULTs to expect back from DoStackSnapshot. However, there are some fringe cases where you can get back an HRESULT that's not as descriptive as you might like. E_FAIL I don...

8/25/10 Update: The sample code linked below is now also available on the MSDN Code Gallery SigParse page. If your profiler plays with metadata, you've undoubtedly come across signature blobs. They’re used to encode type information for method...

Believe it or not, my last (rather large) post on stack walking actually left out several miscellaneous details about using DoStackSnapshot. I'll be posting those details separately. We'll start off with some light reading on exception filters. No deadlocks...

Introduction This article is targeted toward profiler authors, and anyone interested in building a profiler to examine managed applications. I will describe how you can program your profiler to walk managed stacks in version 2.0 of the Common Language...

Howdy! I'm David Broman, and I've been a developer on the Common Language Runtime for about a year, focusing on the Profiling API with Jonathan Keljo , Rico Mariani , and many others. Before the CLR, I worked in various MSN groups, including the MSN...