> On Mar 14, 2016, at 3:08 PM, Jens Alfke <j...@mooseyard.com> wrote: > > >> On Mar 14, 2016, at 1:58 PM, Jim Ingham <jing...@apple.com> wrote: >> >> You can build a dSYM for any linked image. The only thing you can't build >> it for is object and archive files. Whether to do it or not is just a >> tradeoff between build time & preserving debug information long term. > > Thanks … but I’m not getting any insight from that. How about some specific > questions, if I may: > > If I build a static library (.a file) that another developer will link into > their app, do I need to provide a dSYM file too, or does the library already > include all the debug info? > > What about a framework (with a dylib), again to be used in another > developer’s app? Is there any use for a dSYM file with that? (And if so where > does it go? Inside the .framework somewhere?) > > I think I’m generally unclear about what uses dSYM files. Just LLDB? And how > does it find them?
AFAIK, no one distributes dSYMS—they are for the source developer’s purposes. If you really wan to give developers the ability to debug your libraries, just give them the “debug” versions with all symbols intact. Otherwise, Objective-C keeps enough info for someone to (usually) figure out whether a crash is in their code or yours; Swift I don’t know. HTH, Keary Suska Esoteritech, Inc. "Demystifying technology for your home or business" _______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (Xcode-users@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to arch...@mail-archive.com
