Hi Rishan,
No. The debugger isn't going to care about symbols for your assembly. We
use tokens to identify the addresses of functions, etc. Symbols are not
necessary.
If the debugger says that a thread is not a managed thread, it's not. You
can easily see managed code if you do a kb or a kp on a thread. If you see
no information other than the address in a frame, that usually indicates
managed code running in that thread. However, in any case, if a thread
says that it's not managed, it's not.
Jim Cheshire [MSFT]
MCP+I, MCSE, MCSD, MCDBA
ASP.NET Developer Support
(e-mail address removed)
This post is provided "AS-IS" with no warranties and confers no rights.
--------------------
| From: "Rishan" <
[email protected]>
| References: <
[email protected]>
<
[email protected]>
| Subject: Re: Getting proper Stack information from memory dump
| Date: Thu, 11 Nov 2004 09:56:06 -0500
| Lines: 108
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
| X-RFC2646: Format=Flowed; Original
| Message-ID: <
[email protected]>
| Newsgroups: microsoft.public.dotnet.framework.aspnet
| NNTP-Posting-Host: 206.47.190.38
| Path:
cpmsftngxa10.phx.gbl!TK2MSFTFEED02.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13
phx.gbl
| Xref: cpmsftngxa10.phx.gbl microsoft.public.dotnet.framework.aspnet:275332
| X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet
|
| Hi,
|
| I just would like to confirm that in order to see detailed stack
| information, the original ASP.net app that I'm trying to debug must have
| been built in "Debug" mode. The dump I currently have is about a week
old,
| when the app in production was built in "Release" mode. When I try to
view
| stack information, it says the thread is not a managed thread. If it had
| been built in Debug mode, it would have recognized the thread as managed
| correct?
|
| Thanks,
|
| Rishan
|
| | > Hi Rishan,
| >
| > As Bruce said, you want to use the SOS extension for debugging managed
| > code. You can get it from the v1.1.4322 folder. Open your dump in
Windbg
| > and then enter the following command to load it:
| >
| > load c:\\windows\\microsoft.net\\framework\\v1.1.4322\\sos
| >
| > After it's loaded, you can use several methods to view the stack:
| >
| > !clrstack
| >
| > That will show you managed code in the stack. You can get more detail
by
| > running:
| >
| > !clrstack -a
| >
| > If you've already got Perfmon data that shows which threads are the
issue,
| > that should be all you need. If you'd like even more information on
those
| > threads, try this:
| >
| > !dumpstack
| >
| > That will give you a lot more information.
| >
| > Let me know if that helps you.
| >
| > Jim Cheshire [MSFT]
| > MCP+I, MCSE, MCSD, MCDBA
| > ASP.NET Developer Support
| > (e-mail address removed)
| >
| > This post is provided "AS-IS" with no warranties and confers no rights.
| >
| >
| > --------------------
| > | From: "Microsoft News Server" <
[email protected]>
| > | Subject: Getting proper Stack information from memory dump
| > | Date: Tue, 9 Nov 2004 14:45:35 -0500
| > | Lines: 26
| > | X-Priority: 3
| > | X-MSMail-Priority: Normal
| > | X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
| > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
| > | X-RFC2646: Format=Flowed; Original
| > | Message-ID: <
[email protected]>
| > | Newsgroups: microsoft.public.dotnet.framework.aspnet
| > | NNTP-Posting-Host: 206.47.190.38
| > | Path:
| >
cpmsftngxa10.phx.gbl!TK2MSFTNGXA03.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP10
| > phx.gbl
| > | Xref: cpmsftngxa10.phx.gbl
| > microsoft.public.dotnet.framework.aspnet:274812
| > | X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet
| > |
| > | Hi,
| > |
| > | I am currently having a problem with random, intermittent lock ups in
my
| > | ASP.net application on our production server (99% CPU usage by 3
| > threads,
| > | indefinately). I currently use IIS Debug Tools to do a memory dump of
| > the
| > | app when the lock up occurs, however the stack information is not very
| > | useful.
| > |
| > | I have just put a new build of our system onto production, and this
| > build
| > is
| > | a "Debug" build as opposed to a "Release" build. I am hoping to get
more
| > | information from the dump, like which lines of code are being
executed
| > in
| > | the web app.
| > |
| > | Is there anything else I need to setup in order to get this level of
| > detail
| > | out of the dump. Right now, I am just getting Kernel calls, and the
| > three
| > | threads always lock up with the last call being:
| > |
| > | KERNEL32!lstrcmpiw+0xbz
| > |
| > | I am using Windbg to load and view the memory dump files.
| > |
| > | Thanks,
| > |
| > | Rishan
| > |
| > |
| > |
| >
|
|
|
