it's even worse:
filtering the according compiler switches (-Zi
-Fd$(MISC)$/_ooo_st_$(TARGET).PDB) from the compared strings reenables PCH
usage. unfortunately the compiler now refuses to use the generated *.pch file as
the .PDB name stored inside the .pch file differs from that used to compile the
c++ file...

it may be an option to use "-Z7 -Yd" insted of "-Zi
-Fd$(MISC)$/_ooo_st_$(TARGET).PDB" and get rid of the .pdb files in the compile
step completely.

as requested

Crash report resolving along with /Z7 looks good in module VCL.

According to MSDN documentation /Yc /Yd might cause link error if procompiled
headers don't contain function definitions. Missing symbols have to be specified
by /YI. To ensure that this will not cause trouble a complete rebuild of all
modules (build OOo from scratch) is necessary.

When using /Z7 instead of /Zi all .obj files must be available for JIT debugging
with /Zi the .PCB with type infos in wntmsci10.pro/misc were suitable. But this
will not affect the build as the complete source output tree is always available
in OOo's build environment.

Created attachment 41995 [details]
proposed fix

this issue depends on cws pchfix04 as it will bring wider usage of pch

patch applied in pchfix04 now. ENABLE_CRASHDUMP and PCH now coexist.

complete build dtill pending

unfortunately these switches cause some of the large .lib files used to detect
library exports to hit some kind of size limit :(

tweaking process to support more than on lib and splitting candidates into two
pieces...

.

useing "-Z7 -Yd"

Seen on MWS, closing