How to create a dSYM bundle with swiftmodule in it

Thanks! I initially thought that there could be separate swiftmodule files because I saw that in Apple's LLDB source code, SwiftASTContext::CreateInstance actually looks for path "Contents/Resources/Swift/<arch>". If the swiftmodule is embedded in DWARF, then what's the purpose of this code? Or, this means when we are using swiftinterface files, we put them into seperate folders, but when swiftmodule wins over swiftinterface, we emit it in __swit_ast section? Not sure if I understand this right.

The swiftmodule is a binary dump of compiler state; to use it the version of swift contained in lldb must match the version of the compiler that built the swiftmodule. The swift interfaces are textual and (except for source breaking compiler changes) any version of lldb can use them. But swift interface files only contain public interfaces, which renders them less useful for debugging the framework. So the best course is to include both artifacts in the dSYM, use the swiftmodule if you can, and fall back to the swift interface if there's a mismatch between compiler versions.

I'm trying to find a way if the symbols from a static library have made their way into app's dSYM. For assessing that I did otool -v myApp.dSYM, but I'm getting one of -fahlLtdoOrTMRIHCGScisPx or --version must be specified error. Can clarify what you meant and if possible mention a way to validate if the symbols from my .a have made into the app's dSYM?

or perhaps as long as my app works and my has a proper dSYM, then I'm to safely assume that the dSYM will be generated for the static library as well?

otool, nm and Co. don't do the job of finding the binary in the dSYM. You have to explicitly run them on <binary>.dSYM/Contents/Resources/DWARF/<binary>. For listing symbols you want to use nm - otool lists sections & load information, nm lists symbol information.