How to force the loading of symbols?

WINDBG
1

I’m debugging a system crash on an old software release, but I don’t
have the correct .PDB symbol file for one of the modules. I do have the
symbols for the build before and after that release, though. I tried
using those, but WinDbg didn’t feel that they matched. I did a TOUCH to
change the date on the build after one to the same date and time (and
also one minute after) as the module’s time, but WinDbg still didn’t
like it. The error (looking at !sym noisy) is “mismatched pdb”.

I understand that using slightly incorrect PDBs can lead to confusion,
but it’s the best that I can do.

Is there some way to force a .PDB to be loaded?

2

.symopt LOAD_ANYTHING

.reload /f /i

quoting out of memory but im 99 % sure im right
check symopt in windbg help if there are syntax problems

On 1/19/08, Taed Wynnell wrote:
>
>
> I’m debugging a system crash on an old software release, but I don’t have
> the correct .PDB symbol file for one of the modules. I do have the symbols
> for the build before and after that release, though. I tried using those,
> but WinDbg didn’t feel that they matched. I did a TOUCH to change the date
> on the build after one to the same date and time (and also one minute after)
> as the module’s time, but WinDbg still didn’t like it. The error (looking
> at !sym noisy) is “mismatched pdb”.
>
> I understand that using slightly incorrect PDBs can lead to confusion, but
> it’s the best that I can do.
>
> Is there some way to force a .PDB to be loaded?
> —
> You are currently subscribed to windbg as: unknown lmsubst tag argument: ‘’
> To unsubscribe send a blank email to
> xxxxx@lists.osr.com

3

a quick google confirms that im right

you can also use its hex equivalent which is .symopt +0x40

0:000>. Symopt +0 x40
Symbol options are 0x30277: Symbol options are 0x30277:
0x00000001 - SYMOPT_CASE_INSENSITIVE
0x00000002 - SYMOPT_UNDNAME
0x00000004 - SYMOPT_DEFERRED_LOADS
0x00000010 - SYMOPT_LOAD_LINES
0x00000020 - SYMOPT_OMAP_FIND_NEAREST
0x00000040 - SYMOPT_LOAD_ANYTHING <------------------------------
0x00000200 - SYMOPT_FAIL_CRITICAL_ERRORS
0x00010000 - SYMOPT_AUTO_PUBLICS
0x00020000 - SYMOPT_NO_IMAGE_SEARCH

On 1/19/08, raj_r wrote:
> .symopt LOAD_ANYTHING
>
> .reload /f /i
>
> quoting out of memory but im 99 % sure im right
> check symopt in windbg help if there are syntax problems
>
>
>
> On 1/19/08, Taed Wynnell wrote:
> >
> >
> > I’m debugging a system crash on an old software release, but I don’t have
> > the correct .PDB symbol file for one of the modules. I do have the symbols
> > for the build before and after that release, though. I tried using those,
> > but WinDbg didn’t feel that they matched. I did a TOUCH to change the date
> > on the build after one to the same date and time (and also one minute after)
> > as the module’s time, but WinDbg still didn’t like it. The error (looking
> > at !sym noisy) is “mismatched pdb”.
> >
> > I understand that using slightly incorrect PDBs can lead to confusion, but
> > it’s the best that I can do.
> >
> > Is there some way to force a .PDB to be loaded?
> > —
> > You are currently subscribed to windbg as: unknown lmsubst tag argument: ‘’
> > To unsubscribe send a blank email to
> > xxxxx@lists.osr.com
>