Is it possible to (re)create a PDB file after a DLL is made?

That seems to be not possible. Have a look at this here: Why does Visual Studio require debugger symbol files to exactly match the binary files that they were built with?

That seems to be not possible. Have a look at this here: Why does Visual Studio require debugger symbol files to exactly match the binary files that they were built with? Or this article: PDB Files: What Every Developer Must Know Quote out of "PDB Files: What Every...": The extremely important part is how the debugger knows this is the exact matching PDB file for this binary.

That's done through a GUID that's embedded in both the PDB file and the binary. If the GUID does not match, you certainly won't debug the module at the source code level. The .

NET compiler, and for native the linker, puts this GUID into the binary and PDB. Since the act of compiling creates this GUID, stop and think about this for a moment. If you have yesterday's build and did not save the PDB file will you ever be able to debug the binary again?

No! This is why it is so critical to save your PDB files for every build. Because I know you're thinking it, I'll go ahead and answer the question already forming in your mind: no, there's no way to change the GUID.

1 Looks like you are right. But it looks like chkmatch can be used in some cases: debuginfo. Com/tools/chkmatch.

Html – Arve Dec 8 at 12:54 Wow, interesting link! Ok, usually it is not possible. I hope that chkmatch can help you.

– Markus Dec 8 at 12:58.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.