4

I'm trying to build a cmake solution using Incredibuild 5.0 on windows and get PDB management errors in a couple of projects:

Fatal error:
    Failed to notify object at 0x06C150A0, class is TWaitObjectThread_Notify
    PDB Management: Internal Error: Cannot apply file changes while file is being closed: xxxxx.pdb

I thought it might have been the order of .cpp files in the cmakefilelist, but that's not made any difference.

Damien Ryan
  • 1,591
  • 1
  • 15
  • 34
  • 1
    What was the question exactly? This is good question for Incredibuild support, because similar problem was addressed in http://www.incredibuild.com/incredibuild-version-history.html#ch461 Perhaps it is just v5.0 regression. – Sergei Nikulov Apr 10 '14 at 05:45
  • I suppose the question was if there was a magic option I could pass through. I did notice it in the release notes, so I'll get in touch with them. Thanks! – Damien Ryan Apr 10 '14 at 09:44
  • there is no 5.0 yet – Sergei Krivonos Feb 04 '20 at 12:59

2 Answers2

7

There are several things that can cause this. The most popular one is that you have two different projects that are trying to access the same PDB file. The reason you are only seeing this with IncrediBuild is because with IncrediBuild many of your projects are being executed in parallel (when in standalone the projects are executed sequentially). Detect the project that fail and verify whether you have another project that executes in parallel to this one and direct it's PDB to another PDB file. If this is not the case, let me know, there are other less common scenarios.

(Disclaimer: I'm an IncrediBuild employee)

Dori
  • 470
  • 2
  • 6
4

Of course, it was a problem with our build system trying to write 32- and 64-bit versions of the same library to the same filename. Building serially hid the error, but parallel builds highlighted the problem.

Damien Ryan
  • 1,591
  • 1
  • 15
  • 34