怪异的X $ C $Ç链接错误我从来没有说＆QUOT见过;断言失败＆QUOT; [英] Weird xCode linker error I've never seen before saying "Assertion failed"

问题描述

通过内置团结这个游戏，并管理过一次到x code编译。没有任何明显的变化，但是，这种错误信息变成了。我不明白的地方开始寻找一个解决方法，但也许有人有线索？我见过类似的通过搜索寻找错误，虽然修复相比，雷显得随意。

Built this game through Unity, and managed to compile through xCode once before. Without any apparent changes, however, this error message turns up. I don't understand where to start looking for a fix, but maybe someone else have a clue? I've seen similar looking errors through searches, though the fixes seem arbitrary compared to mine.

任何人能提供一些线索？谢谢!!

Anyone able to shed some light? Thank you!!

0 0x1034de0e7 __assert_rtn + 144
1 0x10351350c档案::文件＆LT;臂GT; :: makeObjectFileForMember（存档::文件＆LT;臂GT; ::进入常量*）常量+ 1142
2 0x103512c9a档案::文件＆LT;臂GT; :: forEachAtom（LD ::文件:: AtomHandler＆放大器;）常量+ 416
3 0x10352a6a1 LD ::工具:: InputFiles :: forEachInitialAtom（LD ::文件:: AtomHandler和放大器;，LD ::内部和放大器;）+ 465
4 0x10353490e LD ::工具::解析器解析::（）+ 48
5 0x1034dec47主+ 679
链接器快照创建于：
    /tmp/wingOstar-2014-09-26-171939.ld-snapshot
LD：断言失败：（！memberIndex = 0），函数makeObjectFileForMember，文件/SourceCache/ld64/ld64-236.4/src/ld/parsers/archive_file.cpp，线路355。
铿锵：错误：连接命令，退出code 1（使用-v看看调用）

推荐答案

这似乎是错误的孩子的X code语言开发人员希望你永远不会真正看到...

This seems like the kid of error the Xcode developers hope you never actually see...

这消息可能是最有用的搜索对抗将是 LD的部分：断言失败：（memberIndex！= 0），因为这是根的错误，而不是支持信息。

The part of that message that is likely most useful for searching against will be the ld: Assertion failed: (memberIndex != 0), since that is the root of the error rather than supporting information.

我可能会发现你做了同样的几个来源，但他们表明，这是腐败的资源X $ C $的c之一引起试图程序进行链接，而不是立即通过自己的code引起的一些东西。一个文件变得有些外部动作损坏会解释如何能尽管在你的程序源文件中没有明显的变化发生了。

I probably found the same few sources you did, but they indicated that this is caused by corruption in one of the resources Xcode is trying to link your program against, rather than something immediately caused by your own code. A file becoming corrupted by some external action would explain how this can happen despite no obvious changes in your program source.

所以处理这种显而易见的建议是通过确保无论是导致它被重新编译来修复损坏。要做的第一件事就是彻底清理项目，使年龄不precompiled文件的使用和所有你自己的code的重建。由于您的错误中提到的源缓存，这里遵循的建议来擦拭的所有的缓存，而不仅仅是那些由产品展示 - >清洁选项清除。

So the obvious suggestion for fixing this would be to repair the corruption by making sure whatever is causing it gets recompiled. The first thing to do is to completely clean your project so that no older precompiled files are used and all of your own code is rebuilt. Since your error mentions a source cache, follow the recommendation here to wipe all caches, not just those cleared by the Product->Clean option.

该错误消息也给出了建议，使用 -v 标记，看看 LD 实际上是干什么的，它可以帮助你缩小哪些对象文件可能已损坏（通过展示哪些是实际使用）。要添加标记，去建立在项目的设置设置，再往Linking->其他连接器选项，并添加 -v 来的。一旦你重建项目，看看报表导航器面板生成的消息，并展开链接消息链接对象的完整列表。如果这些选项指的是你提供的库，考虑删除和重建它们，清洗，再重新生成项目前。

The error message also gives a suggestion to use the -v flag to see what ld is actually doing, which may help you narrow down which object files could be corrupt (by showing you which ones are actually used). To add the flag, go to Build Settings in your project's settings, go down to Linking->Other linker flags, and add -v to those. Once you've rebuilt the project, look at the Build messages in the Report Navigator panel, and expand the linker messages for a full list of linked objects. If any of these options refer to libraries you provided, consider deleting and rebuilding them, before cleaning and rebuilding your project again.

这篇关于怪异的X $ C $Ç链接错误我从来没有说＆QUOT见过;断言失败＆QUOT;的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！