从命令行生成的.dSYM文件（Mac） [英] .dSYM files generated from command line (Mac)

问题描述

我刚刚开始用C语言编写代码，并运行其他人的Makefile，默认C编译器设置为gcc。我在Mac OSX 10.8 Mountain Lion上，我相信我用XCode Command Line Tools安装了编译器。在命令行运行make之后，我得到了每个程序的烦人的.dSYM文件。我读过这些是调试文件，但它们真的有必要吗？有没有办法阻止它们从命令行生成？

解决方案

是的，dSYM文件是必需的。具体而言，它们包含Xcode调试版本中包含的符号表;发布版本将符号放在这个单独的文件中。如果你需要分析一个发布版本的堆栈跟踪，你需要这个。并且确保不会丢失文件，因为再次执行构建，即使源代码完全相同，也不会生成可用的dSYM文件。每个构建都有一个UUID，并且每个构建都会随着每个构建而更改，即使源未更改也是如此。 （我想它包括一个时间戳，甚至是一个随机数。）

如果你扔掉了dSYM文件，那么如果你突然发现你的应用崩溃了很多，你可能会对不起。

I just started coding in C, and ran someone else's Makefile with the default C compiler set to gcc. I am on Mac OSX 10.8 Mountain Lion and I believe I installed the compiler with "XCode Command Line Tools." After running "make" on command line, I get these annoying .dSYM files for each program. I read that these are debug files, but are they really necessary? Is there any way to prevent them from being generated from command line?

解决方案

Yes, the dSYM files are necessary. Specifically, they contain the symbol tables that are included within Xcode debug builds; release builds put the symbols in this separate file. If you ever need to analyze a stack trace from a release build you will need this. And make sure you don't lose the files, because doing the build again, even if the source is absolutely the same, won't produce a usable dSYM file. Each build is given a UUID and that changes with each build, even if the source has not changed. (I guess it includes a timestamp or even a random number.)

If you throw away the dSYM files, then if you suddenly find your app crashing a lot, you may be sorry.

这篇关于从命令行生成的.dSYM文件（Mac）的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！