
Identekit (Community Member) asked a question.
In the screenshot below you can see that the PDB file has been uploaded.
...but after the Prescan the file is marked as not found.
It is interesting to note the long path that presedes the PDB file now. I'm not sure where that is coming from or why Veracode is looking in a location it would never have access to. Perhaps this is something being referenced in the EXE?
.png)
I have now been told that this issue should be resolved with a 20.8 release. However, Veracode Support would not tell me when this 20.8 release will be deployed....So, given all that I thought I'd share the solution that I got working.
As it turns out, Veracode renames files that contain parenthesis, replacing the parentheses with underscores. For example, if the following two files, "TestApplication (v1.2.3).exe" and "TestApplication (v1.2.3).pdb", are uploaded to Veracode they will be renamed to "TestApplication _v1.2.3_.exe" and "TestApplication _v1.2.3_.pdb". The problem with strategy is that the EXE is still looking for a symbols PDB file with the original name containing parenthesis.
To solve this I just renamed my application and remove the parenthesis.
This issue caused me so much grief, false positives, bad mitigations and hours of lost time I'll never get back. I cannot for the life of me figure out why Veracode developers thought it would be a good idea to rename the files that are uploaded. Especcially when, as developers, they should know that applications reference other things and when referenceing other things names matter. But they did! Hopefully this supposed 20.8 release will get released sooner rather than later.