Can someone explain this git commit 47536dcd?
Are the pdb's to be included in the dev-builds? Are we looking for better error messages on AppVeyor?
Win, FREECAD_RELEASE_PDB by default
Forum rules
Be nice to others! Respect the FreeCAD code of conduct!
Be nice to others! Respect the FreeCAD code of conduct!
Win, FREECAD_RELEASE_PDB by default
"fight the good fight"
Re: Win, FREECAD_RELEASE_PDB by default
The setting is to also create a pdb file for release builds, i.e. it sets the /DEBUG linker option so that in case of a crash we have a meaningful call stack. For the end-users the pdb files are of no interest so no need to add them to the installers. However, for the developers they are useful together with the crash.dmp file which a user must provide then.
Important to know is that the .pdb files contain some signature and only work for the .dll files created at the same time. This means even when relinking a .dll with exactly the same source code then the old .pdb and the new .dll file (or vice versa) cannot be used together to examine a crash.
To keep extra work at a minimum it suffices to upload the .pdb files for official releases only. The .pdb files should then be uploaded as a separate .zip file.
Important to know is that the .pdb files contain some signature and only work for the .dll files created at the same time. This means even when relinking a .dll with exactly the same source code then the old .pdb and the new .dll file (or vice versa) cannot be used together to examine a crash.
To keep extra work at a minimum it suffices to upload the .pdb files for official releases only. The .pdb files should then be uploaded as a separate .zip file.