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

windbg: Unable to verify checksum for <my dll>

3,613 views
Skip to first unread message

Rajesh K Sharma

unread,
Feb 13, 2003, 9:41:08 PM2/13/03
to
Hello Every one,

I am forcing a dr watson crash dump on a process by drwtsn32 -p <pid>
to look into the internal state of my process; I am able to do that
with a good user.dmp file and have confirmed with !sym noisy command
of windbg that my symbol files are placed correctly; i am using
microsoft public symbol server for os symbol files. But windbg keeps
on giving me warning that "Unable to verify checksum for <my dll>".

I have also tried using "symchk" tool from microsoft to verify that
my pdb file is correct for my dll.

Hence inside windbg I am able to see all the threads and corresponding
stack of them for my process, but some how it does not take me to the
correct source file. I also verified with .srcpath command that my
source path is good.

OS I am running on: win2k pro

Help is greatly appreciated.

Regards- Rajesh

Pat

unread,
Feb 14, 2003, 2:54:01 AM2/14/03
to
The checksum information won't be in the dll itself (it will be in the
symbols) unless you compile w/the /Release flag.

Pat

"Rajesh K Sharma" <rsh...@websense.com> wrote in message
news:d1b925e1.03021...@posting.google.com...

Rajesh K Sharma

unread,
Feb 14, 2003, 11:25:21 AM2/14/03
to
Thanks for the reply Pat. I had it bit resolved though warning
messages are still appearing. I have confirmed that now I build my
dlls with /debug information. But while loading my symbols windbg
still complains with the same warning

"*** WARNING: Unable to verify checksum for C:\Program
Files\Websense\WDC\WsCAMAgent.dll"

Thanks - rsh...@websense.com

"Pat" <patf...@online.microsoft.com> wrote in message news:<Cf13a.95336$iG3.13242@sccrnsc02>...

Pat

unread,
Feb 14, 2003, 12:21:17 PM2/14/03
to
You also need the /Release in addition to the /debug.

David Holcomb [MS]

unread,
Feb 15, 2003, 3:11:16 AM2/15/03
to
What does "!lmi lscamagent" show for the checksum? You should be able to do
a "!dh lscamagent" to see the image headers. If the checksum shows up as
zero I would suspect the problem is with your build environment not adding
the checksum info to the image.

Are you also linking with /debugtype:both and compiling with /Zi?


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


"Pat" <patf...@online.microsoft.com> wrote in message

news:hA93a.101865$tq4.3825@sccrnsc01...

Rajesh K Sharma

unread,
Feb 18, 2003, 3:20:32 PM2/18/03
to
Thanks for the reply, if I do what you say I did see the check sum as
0, but I am building with /Zi switch and default /debugtype switch, I
mean I haven't added any special debug type which I suppose should be
microsoft format.

And you are saying that my build environment is not adding checksum
information into the image, what do I need to get that, thanks again.

"David Holcomb [MS]" <dhol...@microsoft.com> wrote in message news:<3e4df632$1...@news.microsoft.com>...

Pat

unread,
Feb 18, 2003, 8:50:16 PM2/18/03
to
In the linker command line add /Release. That will add the checksum to the
dll.

Pat

"Rajesh K Sharma" <rsh...@websense.com> wrote in message

news:d1b925e1.0302...@posting.google.com...

0 new messages