Re: Function names for managed callstack under SOS debugging of .NET 2.0 app
- From: Mike Blake-Knox <mikebk@xxxxxxxxxxxxx>
- Date: Wed, 12 Jul 2006 15:50:33 -0400
In article <QIFjFQWpGHA.2028@xxxxxxxxxxxxxxxxxxxxx>, Jeffrey Tan[MSFT]
wrote:
0012F014 00F40300 SOSdebuggingTest.Form1.button1_Click(System.Object,
System.EventArgs)
I notice the stack dump doesn't include file/line number information.
What causes this? Also, your traceback doesn't seem to show where in
button1_Click the exception was taken. How can you use SOS to see where
the exception actually occurred?
thanks
Mike
.
- References:
- Function names for managed callstack under SOS debugging of .NET 2.0 app
- From: Daniel Bowen
- RE: Function names for managed callstack under SOS debugging of .NET 2.0 app
- From: "Jeffrey Tan[MSFT]"
- Function names for managed callstack under SOS debugging of .NET 2.0 app
- Prev by Date: Debugging with dumps
- Next by Date: Re: Function names for managed callstack under SOS debugging of .NET 2.0 app
- Previous by thread: RE: Function names for managed callstack under SOS debugging of .NET 2.0 app
- Next by thread: Re: Function names for managed callstack under SOS debugging of .NET 2.0 app
- Index(es):