dsymutil

Received this error message during GenerateDSYMFile phase for an iOS app: /Users/name/Library/Developer/Xcode/DerivedData/ModuleCache/HASH/FrameworkName-HASH: Clang modules are expected to have exactly 1 compile unit. Command /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/dsymutil failed with exit code 1 Deleted: ~/Library/Developer/Xcode/DerivedData And was able to build again. 来源： https://stackoverflow.com/questions/34209145/how-to-debug-dsymutil-error-clang-modules-are-expected-to-have-exactly-1-compi

I tried with extern void __NSAutoreleaseNoPool(void* obj); but that results in an unresolved symbol when linking (not sure what Framework it needs, though). I also tried dlsym(RTLD_DEFAULT, "__NSAutoreleaseNoPool") but that just gives be NULL . And I tried with _dyld_lookup_and_bind and NSLookupSymbolInImage but they also don't work. dsymutil and nm both find the symbol, though: $ dsymutil -s --arch=x86_64 ---------------------------------------------------------------------- /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation -----------------------------------------

Where/how does Apples GCC store DWARF inside an executable? I compiled a binary via gcc -gdwarf-2 (Apples GCC). However, neither objdump -g nor objdump -h does show me any debug information. Also libbfd does not find any debug information. (I asked on the binutils-mailinglist about it here .) I am able however to extract the debugging information via dsymutil (into a dSYM). libbfd is also able to read those debug info then. Jason Molenda On Mac OS X there was a decision to have the linker ( ld ) not process all of the debug information when you link your program. The debug information is often