> Actually the issue I have is I have the proper binaries, and the source code
> as was used to create the binaries, but if I create a new PDB I cannot load
> it (the original PDB was not saved with the build).

> It would be nice to be able to force the loading of the PDB if you know that
> everything is identical (it is built with the same code base on the same computer
> from the same directory...)
>

"Oleg Starodumov" wrote:

>
> > Actually the issue I have is I have the proper binaries, and the source code
> > as was used to create the binaries, but if I create a new PDB I cannot load
> > it (the original PDB was not saved with the build).
>
> So, what message is displayed by the debugger in Modules window
> for those modules? (Just to be sure)
>
> > It would be nice to be able to force the loading of the PDB if you know that
> > everything is identical (it is built with the same code base on the same computer
> > from the same directory...)
> >
>
> See the article referenced in my first reply, it describes what to do in this situation:
> http://www.debuginfo.com/articles/debuginfomatch.html#loadunmatched
>
> If you use WinDbg to debug the dump, execute the following commands to load
> the unmatched PDB files:
> !sym noisy
> ..symopt+0x40
> ..reload /f YourDll.dll
> (repeat .reload for all needed modules)
>
> If something still does not work, please post the output produced by these commands.
>
> If you want to use VS.NET debugger, you can try this tool
> to force the executables and PDB files match:
> http://www.debuginfo.com/tools/chkmatch.html
>
> Regards,
> Oleg
>
>
>
>
>
>
>
>
>
>
>
>