3

I know that I should avoid it as long as possible but let's talk about urgent cases.

What's the chances that .pdb file generated from the same source code with the same libraries produces different result on every build?

Yes, I know that it will differ in GUID but I can change it manually.

Suppose that I don't have a corresponding .pdb file but I know which source code was used to compile the specified product's version.

Matt Johnson-Pint
  • 230,703
  • 74
  • 448
  • 575
FrozenHeart
  • 19,844
  • 33
  • 126
  • 242
  • I suspect you're asking this question [here](http://stackoverflow.com/questions/744870/how-can-you-change-an-age-mismatched-pdb-to-match-properly) – UKMonkey Oct 03 '16 at 10:29
  • @UKMonkey I'm not asking about how to change the GUID. Please reread my question – FrozenHeart Oct 03 '16 at 10:41
  • Are you asking if the compiler output is deterministic? –  Oct 03 '16 at 10:50
  • @Raw N Yeah, something like that. I know that it generally doesn't but I don't have any other option at the moment – FrozenHeart Oct 03 '16 at 10:50

1 Answers1

0

What I know that you could find the mismatched information for different pdb files with the same source code like this blog except the GUID:

https://blogs.msdn.microsoft.com/junfeng/2007/11/05/mismatched-pdbs-why/

A thread also shared some information about the timestamp which should be match here:

Compiler PDB file and the Linker PDB file

Community
  • 1
  • 1
Jack Zhai
  • 6,230
  • 1
  • 12
  • 20
  • I know. Please reread the question -- "Yes, I know that it will differ in GUID but I can change it manually" – FrozenHeart Oct 04 '16 at 09:54
  • @FrozenHeart, So the real issue is that you want to know that whether there are other differences except the GUID for PDB files, am I right? – Jack Zhai Oct 05 '16 at 01:10