Description
As per discussion on email, we want to ensure that Windows issues can be debugged efficiently, which requires that we:
1. Select "Release with Debug Info"- this will create PDB files during the build.
2. Save the relevent PDB files (memcached.pdb, ep.pdb, etc) somewhere.
To actually debug after the fact (on say a different machine) you need:
a) The original .exe / .dll files from the build (which are packaged up already).
b) The aforementioned PDB files (in any path).
c) Matching source (in any path) - which we can checkout using the informaiton in the manifest.
Attachments
Issue Links
- relates to
-
MB-13723 [Linux] Build and package with debugging info
- Closed
For Gerrit Dashboard: MB-13722 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
47626,4 | MB-13722: RelWithDebInfo optimization flags should match Release | master | tlm | Status: MERGED | +2 | +1 |
47682,3 | MB-13722: Generate and save Windows debug (PDB) files. | master | build | Status: MERGED | +2 | +1 |
47687,2 | MB-13722: Adjust PDB archive filename to match format of .exe | master | build | Status: MERGED | +2 | +1 |
48241,2 | MB-13932: Mark CMAKE_{C,CXX}_FLAGS... as CACHE to ensure they take effect | master | tlm | Status: ABANDONED | 0 | +1 |