all groups > dotnet clr > june 2006 >
You're in the

dotnet clr

group:

Thread stack (not call stack)


Thread stack (not call stack) William Sullivan
6/29/2006 9:36:02 AM
dotnet clr:
Is there any way to examine a given thread's stack? As in, the list of
variables currently accessible by the executing code on a given thread, plus
Re: Thread stack (not call stack) Willy Denoyette [MVP]
6/30/2006 11:17:02 PM
Not from managed code, you need to run in a native debugger or the Kernel
debugger.

Willy.


"William Sullivan" <WilliamSullivan@discussions.microsoft.com> wrote in
message news:1E6EC8F7-A7B8-4ECA-8596-212BA17F0381@microsoft.com...
| Is there any way to examine a given thread's stack? As in, the list of
| variables currently accessible by the executing code on a given thread,
plus
| their values? TIA!

Re: Thread stack (not call stack) William Sullivan
7/3/2006 5:58:02 AM
Yecch. Ugly. Thanks for the info.

[quoted text, click to view]
RE: Thread stack (not call stack) Peter Ritchie
7/3/2006 12:23:01 PM
See the Managed Stack Explorer [1]

[1] http://www.codeplex.com/Wiki/View.aspx?ProjectName=MSE

--
http://www.peterRitchie.com/
Microsoft MVP, Visual Development - C#


[quoted text, click to view]
Re: Thread stack (not call stack) Peter Ritchie [MVP]
7/14/2006 2:19:02 PM
MSE doesn't currently do this; but it's essentially a managed debugger and
open-source--which a current feature request to display stack variables as
well--so I mentioned it in case he wanted to add that feature to the project.

--
http://www.peterRitchie.com/blog/
Microsoft MVP, Visual Developer - Visual C#


[quoted text, click to view]
Re: Thread stack (not call stack) Willy Denoyette [MVP]
7/14/2006 11:06:21 PM
This doesn't do what the OP is asking for, it only shows stack traces
(frames) not the stack variables.

Willy.

[quoted text, click to view]
| See the Managed Stack Explorer [1]
|
| [1] http://www.codeplex.com/Wiki/View.aspx?ProjectName=MSE
|
| --
| http://www.peterRitchie.com/
| Microsoft MVP, Visual Development - C#
|
|
[quoted text, click to view]
|
| > Is there any way to examine a given thread's stack? As in, the list of
| > variables currently accessible by the executing code on a given thread,
plus
| > their values? TIA!

AddThis Social Bookmark Button