Problem with symbols for mscorwks.dll .NET 1.1 SP!

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Sriram Krishnan - 18 Oct 2004 16:31 GMT

I've already posted this on the vsnet.debugging and the develop.com CLR list
to no avail. This might seem slightly off-topic but any help would be
*deeply* appreciated.

I'm just learning my way around WinDbg and have hit a problem.

I'm trying to debug into a C# application and have been stopped by the
symbols for mscorwks.dll not loading. I've the full download of Win XP SP2
symbols set up as well as the path to Microsoft's symbol server set.
However, I'm still not getting the symbols loaded and it is defaulting to
the export symbols.

Here's the message I get
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
E:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorwks.dll

And here's my symbol path - I've made sure I point to VS.NET's symbols right
at the beginning.F:\symbols is where I've extracted the XP SP2 symbols.

F:\Program Files\Microsoft Visual Studio .NET
2003\SDK\v1.1\symbols;F:\symbols;srv*F:\symbols*http://msdl.microsoft.com/download/symbols;

Am I missing something basic here? Very possible as I'm a newbie to WinDBG
debugging. I'm wondering whether this problem is caused by me having .NET
1.1 with SP1 installed - any chance that the SP1 symbols are different and
havent put up for download yet?

Signature

Sriram Krishnan

http://www.dotnetjunkies.com/weblog/sriram

Reply to this Message

JohnDadd - 18 Oct 2004 20:41 GMT

Sriram,

Using WinDbg to debug a managed application (i.e. C# programs) is probably
not a good idea. You should be using the Visual Studio debugger, if you have
VS installed. If you aren't using VS, you can use the either the DbgClr ( has
a GUI) or the cordbg debugger which is a command line style debugger (i.e. no
GUI).

You can get more info on those .NET debugging tools by going to
http://msdn.microsoft.com/ and searvhing the MSDN library for DbgClr or
cordbg.

> I've already posted this on the vsnet.debugging and the develop.com CLR list
> to no avail. This might seem slightly off-topic but any help would be
[quoted text clipped - 22 lines]
> 1.1 with SP1 installed - any chance that the SP1 symbols are different and
> havent put up for download yet?

Reply to this Message

Sriram Krishnan - 18 Oct 2004 21:13 GMT

Thanks - but the kind of debugging I want to do is not really possible with
VS.NET. I'm looking at stuff like !EEHeap and !EEStack and checking out the
status of various threads etc. sos.dll used along with WinDBG/ntsd is an
amazing tool. Yes - you can load sos.dll in VS 2003 but it doesn't support
everything that WinDBG does

Signature

Sriram Krishnan

http://www.dotnetjunkies.com/weblog/sriram

> Sriram,
>
[quoted text clipped - 43 lines]
>> and
>> havent put up for download yet?

Reply to this Message

JohnDadd - 18 Oct 2004 21:39 GMT

You should be able to do that kind of thing with cordbg. See
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cptools/html/cp
grfruntimedebuggercordbgexe.asp for info on cordbg commands.

> Thanks - but the kind of debugging I want to do is not really possible with
> VS.NET. I'm looking at stuff like !EEHeap and !EEStack and checking out the
[quoted text clipped - 49 lines]
> >> and
> >> havent put up for download yet?

Reply to this Message

Sriram Krishnan - 18 Oct 2004 21:43 GMT

No you can't . For example, if I want to look at *all threads*, I can do a
~* kb. All these are commands that you dont have in cordbg

Signature

Sriram Krishnan

http://www.dotnetjunkies.com/weblog/sriram

> You should be able to do that kind of thing with cordbg. See
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cptools/html/cp
grfruntimedebuggercordbgexe.asp
[quoted text clipped - 62 lines]
>> >> and
>> >> havent put up for download yet?

Reply to this Message

"Jonathan Keljo [MS]" - 28 Oct 2004 20:02 GMT

Hi Sriram,
The symbols for .NET 1.1 SP1 would indeed be different than those for
.NET 1.1 gold--any time you do a new build, the symbols change even if you
made no source changes. However they should be on the public symbol server,
and in fact I'm able to load the symbols for mscorwks.dll (1.1.4322.2022)
on my 1.1 SP1 machine with the public symbol server.

Some questions:

1. What's the version of mscorwks? ("lmv m mscorwks" will show you) It may
be that particular version is somehow not on the server. (If that's the
case, we'll get it up there)
2. Will symbols load from the symbol server for any other Microsoft dlls?
(".reload /f" will force loading of all symbols, then "lm" again to see if,
for example, "ntdll" has symbols loaded) If they don't, there's something
wonky with the symbol path

Jonathan

PS Here's an example of what I tried on my machine, and the results of
successfully loading symbols from the public symbol server:

CommandLine: C:\temp\test.exe
Symbol search path is: C:\Program Files\Microsoft Visual Studio .NET
2003\SDK\v1.1\symbols;C:\temp;srv*C:\temp*http://msdl.microsoft.com/download
/symbols
Executable search path is:
ModLoad: 00400000 00408000 test.exe
ModLoad: 77f50000 77ff7000 ntdll.dll
ModLoad: 79170000 79196000 C:\WINDOWS\system32\mscoree.dll
ModLoad: 77e60000 77f46000 C:\WINDOWS\system32\KERNEL32.dll
ModLoad: 77dd0000 77e5d000 C:\WINDOWS\system32\ADVAPI32.dll
ModLoad: 78000000 78087000 C:\WINDOWS\system32\RPCRT4.dll
(d20.d58): Break instruction exception - code 80000003 (first chance)
eax=00241eb4 ebx=7ffdf000 ecx=00000000 edx=77f51301 esi=00241eb4
edi=00241f48
eip=77f75a58 esp=0012fb38 ebp=0012fc2c iopl=0 nv up ei pl nz na pe
nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000
efl=00000202
ntdll!DbgBreakPoint:
77f75a58 cc int 3
0:000> .sympath
Symbol search path is: C:\Program Files\Microsoft Visual Studio .NET
2003\SDK\v1.1\symbols;C:\temp;srv*C:\temp*http://msdl.microsoft.com/download
/symbols
0:000> sxe ld mscorwks
0:000> g
ModLoad: 70a70000 70ad9000 C:\WINDOWS\system32\SHLWAPI.dll
ModLoad: 7f000000 7f041000 C:\WINDOWS\system32\GDI32.dll
ModLoad: 77d40000 77dcc000 C:\WINDOWS\system32\USER32.dll
ModLoad: 77c10000 77c63000 C:\WINDOWS\system32\msvcrt.dll
ModLoad: 791b0000 79416000
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorwks.dll
eax=00000000 ebx=00000000 ecx=008f0000 edx=00000000 esi=00000000
edi=00000000
eip=7ffe0304 esp=0012f230 ebp=0012f32c iopl=0 nv up ei pl nz na pe
nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000
efl=00000202
SharedUserData!SystemCallStub+0x4:
7ffe0304 c3 ret
0:000> lm
start end module name
00400000 00408000 test (deferred)
70a70000 70ad9000 SHLWAPI (deferred)
77c10000 77c63000 msvcrt (deferred)
77d40000 77dcc000 USER32 (deferred)
77dd0000 77e5d000 ADVAPI32 (deferred)
77e60000 77f46000 KERNEL32 (deferred)
77f50000 77ff7000 ntdll (pdb symbols)
C:\temp\ntdll.pdb\3E7B64D65\ntdll.pdb
78000000 78087000 RPCRT4 (deferred)
79170000 79196000 mscoree (deferred)
791b0000 79416000 mscorwks (deferred)
7f000000 7f041000 GDI32 (deferred)
0:000> .reload /f
Reloading current modules
.*** WARNING: Unable to verify checksum for test.exe
.........
0:000> lm
start end module name
00400000 00408000 test C (private pdb symbols) C:\temp\test.pdb
70a70000 70ad9000 SHLWAPI (pdb symbols)
C:\temp\shlwapi.pdb\41264DB72\shlwapi.pdb
77c10000 77c63000 msvcrt (pdb symbols)
C:\temp\msvcrt.pdb\3D6DD5921\msvcrt.pdb
77d40000 77dcc000 USER32 (pdb symbols)
C:\temp\user32.pdb\40D1D36E2\user32.pdb
77dd0000 77e5d000 ADVAPI32 (pdb symbols)
C:\temp\advapi32.pdb\3D6DE4CE2\advapi32.pdb
77e60000 77f46000 KERNEL32 (pdb symbols)
C:\temp\kernel32.pdb\40D1D0C52\kernel32.pdb
77f50000 77ff7000 ntdll (pdb symbols)
C:\temp\ntdll.pdb\3E7B64D65\ntdll.pdb
78000000 78087000 RPCRT4 (pdb symbols)
C:\temp\rpcrt4.pdb\404930602\rpcrt4.pdb
79170000 79196000 mscoree (pdb symbols)
C:\temp\mscoree.pdb\3B73BB37717C44EC9199E94AC211B20D2\mscoree.pdb
791b0000 79416000 mscorwks (pdb symbols)
C:\temp\mscorwks.pdb\BF456C8C181A446D9ADACE31D7CAB2BD2\mscorwks.pdb
7f000000 7f041000 GDI32 (pdb symbols)
C:\temp\gdi32.pdb\40D1D0CB2\gdi32.pdb

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------

| From: "Sriram Krishnan" <ksriram@NOSPAMgmx.net>
| References: <uG6mugStEHA.1452@TK2MSFTNGP11.phx.gbl>

<EF124DCB-96A3-423A-A5A2-D586D90F3C6D@microsoft.com>
<#77jR#UtEHA.2668@TK2MSFTNGP12.phx.gbl>
<458338C0-9AE7-4346-AF1F-81CFEED5E35A@microsoft.com>

| Subject: Re: Problem with symbols for mscorwks.dll .NET 1.1 SP!
| Date: Tue, 19 Oct 2004 02:13:08 +0530
[quoted text clipped - 8 lines]
| NNTP-Posting-Host: 61.8.144.98
| Path:

cpmsftngxa06.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP11
.phx.gbl

| Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.framework.clr:12015
| X-Tomcat-NG: microsoft.public.dotnet.framework.clr
[quoted text clipped - 3 lines]
|
| > You should be able to do that kind of thing with cordbg. See

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cptools/htm
l/cpgrfruntimedebuggercordbgexe.asp

| > for info on cordbg commands.
| >
[quoted text clipped - 51 lines]
| >> >>
| >> >> F:\Program Files\Microsoft Visual Studio .NET

2003\SDK\v1.1\symbols;F:\symbols;srv*F:\symbols*http://msdl.microsoft.com/do
wnload/symbols;

| >> >> Am I missing something basic here? Very possible as I'm a newbie to
| >> >> WinDBG
[quoted text clipped - 3 lines]
| >> >> and
| >> >> havent put up for download yet?

Reply to this Message

Sriram Krishnan - 28 Oct 2004 21:01 GMT

Thanks for the response. I had resolved this thanks to a post from the
Windbg group where they advised me to download everything from the Symbol
server instead of relying on the local cache

Signature

Sriram Krishnan

http://www.dotnetjunkies.com/weblog/sriram

> Hi Sriram,
> The symbols for .NET 1.1 SP1 would indeed be different than those for
[quoted text clipped - 222 lines]
> | >> >> and
> | >> >> havent put up for download yet?

Reply to this Message

Rate this thread:

Problem with symbols for mscorwks.dll .NET 1.1 SP!

Free Magazines