I've been working on an iPhone application had an issue where dSYM file generation was seg faulting on me.
我一直在开发一个iPhone应用程序，但dSYM文件生成出现了seg错误。
GenerateDSYMFile /Users/kaom/Projects/build/Release-iphoneos/NodeAppGen.app.dSYM /Users/kaom/Projects/build/Release-iphoneos/NodeAppGen.app/NodeAppGen cd /Users/kaom/Projects/Apps/NodeAppGen setenv PATH "/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin:/Developer/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin" /Developer/usr/bin/dsymutil /Users/kaom/Projects/build/Release-iphoneos/NodeAppGen.app/NodeAppGen -o /Users/kaom/Projects/build/Release-iphoneos/NodeAppGen.app.dSYM
GenerateDSYMFile /用户/ kaom /项目/构建/ Release-iphoneos / NodeAppGen.app。dSYM /用户/ kaom /项目/构建/ Release-iphoneos / NodeAppGen。app/NodeAppGen cd /Users/kaom/Projects/Apps/NodeAppGen setenv PATH”/Developer/ platform /iPhoneOS。平台/开发/ usr / bin:/开发/ usr / bin:/ usr / bin:/ bin:/ usr / sbin / sbin”/开发/ usr / bin / dsymutil /用户/ kaom /项目/构建/ Release-iphoneos / NodeAppGen。app / NodeAppGen - o /用户/ kaom /项目/构建/ Release-iphoneos / NodeAppGen.app.dSYM
Command /Developer/usr/bin/dsymutil failed with exit code 11
命令/开发/ usr / bin / dsymutil失败,退出码11
I tracked this bug down to an error in the application's Info.plist file.
我跟踪这个错误到应用程序信息中的一个错误。plist文件。
Instead of
而不是
<key>CFBundleVersion</key>
<string>1.0</string>
I had
我有
<key>CFBundleVersion</key>
<real>1.0</real>
To my knowledge, dSYM file generation is only dependent on the executable and the plist file should not affect the executable. So my question is why did this break dSYM file generation?
据我所知，dSYM文件生成仅依赖于可执行文件，plist文件不应影响可执行文件。我的问题是，为什么会出现这种中断dSYM文件生成的情况?
1 个解决方案
#1
0
Look for an error earlier in the build log, possibly one that didn't actually get parsed out as an explicit error by Xcode.
在构建日志中查找较早的错误，可能是Xcode实际上没有解析为显式错误的错误。
More likely than not, something was chomping on the Info.plist and was mighty confused to find a <real/> instead of a <string/> value.
更有可能的是，一些东西正在吞噬着信息。发现
In any case, file a bug via http://bugreport.applec.om, as having the dev tools produce a useful error message is always desirable.
无论如何，通过http://bugreport.applec文件错误。om，因为让开发工具生成有用的错误消息总是可取的。
#1
0
Look for an error earlier in the build log, possibly one that didn't actually get parsed out as an explicit error by Xcode.
在构建日志中查找较早的错误，可能是Xcode实际上没有解析为显式错误的错误。
More likely than not, something was chomping on the Info.plist and was mighty confused to find a <real/> instead of a <string/> value.
更有可能的是，一些东西正在吞噬着信息。发现
In any case, file a bug via http://bugreport.applec.om, as having the dev tools produce a useful error message is always desirable.
无论如何，通过http://bugreport.applec文件错误。om，因为让开发工具生成有用的错误消息总是可取的。