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

Symbols Mismatch in WinDbg w/ Digitally Signed EXE/DLLs

59 views
Skip to first unread message

chuck_k

unread,
Dec 15, 2009, 12:47:04 PM12/15/09
to
Associated PDBs are rendered useless after using signtool on EXE/DLL. Is
there a way around this? Is there a way to repair the PDB after running
signtool? Thx.

Same issue:
http://www.dumpanalysis.org/forum/viewtopic.php?f=1&t=242

Marc Sherman

unread,
Dec 16, 2009, 4:45:02 PM12/16/09
to

Have you tried to force the pdb for the dll to be loaded?

.reload /i <your.dll>

"chuck_k" <chu...@discussions.microsoft.com> wrote in message
news:69E77FE0-0B25-4DFD...@microsoft.com...

pat styles [microsoft]

unread,
Dec 17, 2009, 2:08:12 PM12/17/09
to
Hello Chuck.

It's been a long time since I've done this, but we signed all the debugger
distribution bits and had no trouble matching PDBs to the binaries. You can
confirm this by simply debugging the latest debugger. All the bits are
signed. Now I am not an expert in the intricacies of signing, but do know
that it can be made to work.

.pat styles [microsoft]

"chuck_k" <chu...@discussions.microsoft.com> wrote in message
news:69E77FE0-0B25-4DFD...@microsoft.com...

chuck_k

unread,
Dec 17, 2009, 3:02:01 PM12/17/09
to
I did try forcing the load (via .reload /i). It worked but they didn't match
up. Stack frames pointed to source file locations that didn't make sense.

"Marc Sherman" wrote:

> Have you tried to force the pdb for the dll to be loaded?
>

> ..reload /i <your.dll>


>
> "chuck_k" <chu...@discussions.microsoft.com> wrote in message
> news:69E77FE0-0B25-4DFD...@microsoft.com...
> > Associated PDBs are rendered useless after using signtool on EXE/DLL. Is
> > there a way around this? Is there a way to repair the PDB after running
> > signtool? Thx.
> >
> > Same issue:
> > http://www.dumpanalysis.org/forum/viewtopic.php?f=1&t=242
>
>

> .
>

chuck_k

unread,
Dec 18, 2009, 10:31:01 AM12/18/09
to
Thanks Pat.

Based on your reply, I tried debugging a more recent build of our product
(also signed) and it worked fine. I also used userdump to create a dump, and
was able to match up symbols in WinDbg. I don't know why I couldn't get
symbols to line up for this one particular build and crash dump. We had
recently started signing our binaries so I "assumed" it to be the culprit.
Sorry for the noise.


"pat styles [microsoft]" wrote:

> Hello Chuck.
>
> It's been a long time since I've done this, but we signed all the debugger
> distribution bits and had no trouble matching PDBs to the binaries. You can
> confirm this by simply debugging the latest debugger. All the bits are
> signed. Now I am not an expert in the intricacies of signing, but do know
> that it can be made to work.
>

> ..pat styles [microsoft]


>
> "chuck_k" <chu...@discussions.microsoft.com> wrote in message
> news:69E77FE0-0B25-4DFD...@microsoft.com...
> Associated PDBs are rendered useless after using signtool on EXE/DLL. Is
> there a way around this? Is there a way to repair the PDB after running
> signtool? Thx.
>
> Same issue:
> http://www.dumpanalysis.org/forum/viewtopic.php?f=1&t=242
>

> .
>

0 new messages