Use dwarf (not dwarf-with-dsym) for Debug builds#766
Merged
theospears merged 1 commit intomasterfrom Apr 11, 2026
Merged
Conversation
Xcode 16's Debug Dylib Support puts all debug info in BeeSwift.debug.dylib inside the app bundle, leaving the main executable as a shim with no DWARF. dsymutil was still running on that shim (because Debug was set to dwarf-with-dsym), producing an empty dSYM and the "empty dSYM file detected" warning on every debug launch. dSYMs aren't needed for local debug builds anyway - the debugger reads DWARF directly. Release remains dwarf-with-dsym. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
warning: (arm64) .../BeeSwift.app/BeeSwift empty dSYM file detected, dSYM was created with an executable with no debug infoemitted on every debug launch.BeeSwift.debug.dylibinside the app bundle, leaving the main executable as a shim with no DWARF.dsymutilwas still running on that shim (because Debug was set todwarf-with-dsym), producing an empty dSYM.dwarf(Xcode's default for Debug). dSYMs aren't needed for local debug builds — lldb reads DWARF directly from object files / dylibs. Release remainsdwarf-with-dsymso archive builds still generate symbols for crash symbolication.Test plan
🤖 Generated with Claude Code