One might expect that the PDBs (debug symbol databases) could be reproduced verbatim by recompiling the source code from the exact same Git tag, but in practice the many variations in compiler version and environment, let alone security mitigations, have long ago made that a thing of the past among compiler vendors.
Hence, each build gets its own UUID which is used to tie back to the relevant PDB files.
Thus, we need to upload our PDBs together with our build, if we want to let software such as VA interpret any debug info.
Good to know...
However, I've been using EDDI with VA and 2 HCS voicepacks for several years now and currently have no issues.
I do use the basic unedited default EDDI installation and stopped creating new personalities a few versions back. I have an Exploration and Multi-purpose personality, but the only changes are which boxes are unchecked from the default. I don't edit any scripts or otherwise vary from the default as I find the tight integration between the voice pack and EDDI works so well that I don't want to mess it up. I stay within my limits, which are considerable when it comes to programming.
My hunch is that current reported issues are from editing errors and not grounded in either EDDI or VA based on my experience of only running the baseline default scripts in EDDI.
I'll run the EDDI default personality for a bit to see if anything pops up.