Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

newbie question: Unable to verify checksum for mscorlib.ni.dll

1,379 views
Skip to first unread message

danj

unread,
Mar 14, 2010, 9:21:39 AM3/14/10
to
Hi,

I'm getting the following warning when I load the mini crashdump:
Unable to load image D:\WINDOWS\assembly
\NativeImages_v2.0.50727_32\mscorlib
\7124a40b9998f7b63c86bd1a2125ce26\mscorlib.ni.dll, Win32 error 0n2
*** WARNING: Unable to verify checksum for mscorlib.ni.dll

I think I have correctly configure the symbol server.
Any ideas what I might be doing wrong?

Kalle Olavi Niemitalo

unread,
Mar 14, 2010, 4:11:35 PM3/14/10
to
danj <dan.j...@gmail.com> writes:

> *** WARNING: Unable to verify checksum for mscorlib.ni.dll
>
> I think I have correctly configure the symbol server.
> Any ideas what I might be doing wrong?

That refers to the checksum in the header of the DLL file.
Apparently, whatever mechanism created the file did not
save a checksum in the header, so the debugger can't check it.
Having or not having symbols does not affect this warning.
If you got this warning for a file of your own, then you could
make it go away by setting the appropriate linker option.
However, as mscorlib.ni.dll looks like a Microsoft file,
it seems best to just ignore the warning for that file.

Apart from the debugger, I know of only one mechanism that
makes any use of the checksum: Windows Installer can check
it and reinstall corrupted files.

danj

unread,
Mar 15, 2010, 4:03:08 AM3/15/10
to
On Mar 14, 10:11 pm, Kalle Olavi Niemitalo <k...@iki.fi> wrote:

Thanks for the reply. What about the fact that the debugger is unable
to load the image of the dll?
Isn't this one of the reasons I'm unable to get a full stack trace?

Dan

Kalle Olavi Niemitalo

unread,
Mar 15, 2010, 4:40:23 AM3/15/10
to
danj <dan.j...@gmail.com> writes:

> What about the fact that the debugger is unable
> to load the image of the dll?

Oops, I didn't notice that.
Win32 error 0n2 means file not found; does the file exist?
Perhaps the crash dump was taken from a computer that has
this file, but you're debugging it on a computer that hasn't.
If so, you could copy the file over and add its directory
to the image path (not the symbol path).

Many DLL and EXE files are also available at the Microsoft
symbol server (so you'd use the SRV syntax in the image path)
but I don't know whether that applies to .NET Framework
native images.

danj

unread,
Mar 15, 2010, 6:18:12 AM3/15/10
to
On Mar 15, 10:40 am, Kalle Olavi Niemitalo <k...@iki.fi> wrote:

Just to make sure I understand -
Can use the SRV syntax in the image path as well (not in the symbol
path)? I tried that but it doesn't seem to make a difference.
I guess the my problem is actually where can I find a copy of the
native .Net framework images?

Thanks,
Dan

Marc Sherman

unread,
Mar 15, 2010, 11:33:30 PM3/15/10
to

IIRC, you need to load managed dumps on a machine that has the exact same
version of the .NET framework that was loaded in the original process.

Marc

"danj" <dan.j...@gmail.com> wrote in message
news:818181b7-21c8-4176...@d27g2000yqf.googlegroups.com...

0 new messages