mirror of
https://github.com/storytold/photocraft.git
synced 2026-11-21 01:18:43 +00:00
package.ps1 now also writes photocraft-<v>-windows-<arch>-symbols.zip with photocraft.pdb and photocraft_cli.pdb from the same optimized build as the signed exes, plus symbols.txt on loading them in WPA, Superluminal or Visual Studio. It's a separate optional asset, so the MSI and portable zip keep their size; the shared release workflow uploads everything in dist/release. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
22 lines
1.2 KiB
Plaintext
22 lines
1.2 KiB
Plaintext
PhotoCraft debug symbols
|
|
|
|
photocraft.pdb and photocraft_cli.pdb are the debug symbols of photocraft.exe and
|
|
photocraft-cli.exe from the release with the same version and architecture as this zip. They
|
|
were written by the same build as those exes, so they match only them: a PDB from a local build
|
|
of the same commit doesn't.
|
|
|
|
They hold PhotoCraft's function names (release builds carry no source line tables), which is
|
|
what a profiler needs to show where the time goes. PhotoCraft doesn't need them to run.
|
|
|
|
To use them, either copy both files next to photocraft.exe (the installer's folder, by default
|
|
C:\Program Files\PhotoCraft), or add this folder to the profiler's symbol path:
|
|
|
|
Windows Performance Analyzer: Trace > Configure Symbol Paths, add this folder, then
|
|
Trace > Load Symbols.
|
|
Superluminal: Settings > Symbols, add this folder as a symbol location.
|
|
Visual Studio: Tools > Options > Debugging > Symbols, add this folder.
|
|
Any tool reading _NT_SYMBOL_PATH: set _NT_SYMBOL_PATH to this folder.
|
|
|
|
When you share a profile in a PhotoCraft issue, say which version and architecture you ran
|
|
(Help > System Info).
|