Info.plist文件处理修改可执行文件
我一直在开发 iPhone 应用程序时遇到一个问题，即 dSYM 文件生成对我来说是段错误。
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
命令 /Developer/usr/bin/dsymutil 失败，退出代码为 11
我将此错误跟踪到应用程序的 Info.plist 文件中的错误。
据
<key>CFBundleVersion</key>
<string>1.0</string>
我
<key>CFBundleVersion</key>
<real>1.0</real>
所知，dSYM 文件生成仅依赖于可执行文件，plist 文件应该不会影响可执行文件。所以我的问题是为什么这会破坏 dSYM 文件生成？
I've been working on an iPhone application had an issue where dSYM file generation was seg faulting on me.
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.dSYMCommand /Developer/usr/bin/dsymutil failed with exit code 11
I tracked this bug down to an error in the application's Info.plist file.
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?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
在构建日志中查找较早的错误，该错误可能实际上并未被 Xcode 解析为显式错误。
更有可能的是，Info.plist 上有东西正在咀嚼，并且非常困惑地找到
/> 无论如何，请通过 http://bugreport.applec.om 提交错误，因为开发工具会生成总是需要有用的错误消息。
Look for an error earlier in the build log, possibly one that didn't actually get parsed out as an explicit error by 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.