2012-11-28 55 views
0

我使用仪器工具(泄漏)来诊断泄漏,但我不太明白我如何可以回溯到我的代码。有谁知道我该如何进一步诊断?xCode&iOS:调试与泄漏

使用Xcode 4.5 &在iPad(iOS 4.3.5)上进行性能分析。

UPDATE:这里是回溯:

thread #4: tid = 0x3203, 0x35dffd7a libicucore.A.dylib`utext_hasMetaData + 546, stop reason = EXC_BAD_ACCESS (code=2, address=0x0) 
    frame #0: 0x35dffd7a libicucore.A.dylib`utext_hasMetaData + 546 
    frame #1: 0x003c17d0 
    frame #2: 0x35da6746 libicucore.A.dylib`icu::RuleBasedBreakIterator::handleNext(icu::RBBIStateTable const*) + 806 
    frame #3: 0x35da6406 libicucore.A.dylib`icu::RuleBasedBreakIterator::next() + 82 
    frame #4: 0x35da5cde libicucore.A.dylib`icu::RuleBasedBreakIterator::following(int) + 218 
    frame #5: 0x35db0538 libicucore.A.dylib`ubrk_following + 8 
    frame #6: 0x32bb0bc8 WebCore`WebCore::textBreakFollowing(WebCore::TextBreakIterator*, int) + 8 
    frame #7: 0x32b9baee WebCore`WebCore::nextBreakablePosition(unsigned short const*, int, int, bool) + 270 
    frame #8: 0x32bd0dc8 WebCore`WebCore::RenderBlock::findNextLineBreak(WebCore::BidiResolver<WebCore::InlineIterator, WebCore::BidiRun>&, bool, bool&, bool&, bool&, WebCore::EClear*) + 6920 
    frame #9: 0x32b8ce02 WebCore`WebCore::RenderBlock::layoutInlineChildren(bool, int&, int&) + 1922 
    frame #10: 0x32b8a1ae WebCore`WebCore::RenderBlock::layoutBlock(bool) + 690 
    frame #11: 0x32b897c2 WebCore`WebCore::RenderBlock::layout() + 26 
    frame #12: 0x32b8b956 WebCore`WebCore::RenderBlock::layoutBlockChild(WebCore::RenderBox*, WebCore::RenderBlock::MarginInfo&, int&, int&) + 414 
    frame #13: 0x32b8b24c WebCore`WebCore::RenderBlock::layoutBlockChildren(bool, int&) + 428 
    frame #14: 0x32b8a1bc WebCore`WebCore::RenderBlock::layoutBlock(bool) + 704 
    frame #15: 0x32b897c2 WebCore`WebCore::RenderBlock::layout() + 26 
    frame #16: 0x32b8b956 WebCore`WebCore::RenderBlock::layoutBlockChild(WebCore::RenderBox*, WebCore::RenderBlock::MarginInfo&, int&, int&) + 414 
    frame #17: 0x32b8b24c WebCore`WebCore::RenderBlock::layoutBlockChildren(bool, int&) + 428 
    frame #18: 0x32b8a1bc WebCore`WebCore::RenderBlock::layoutBlock(bool) + 704 
    frame #19: 0x32b897c2 WebCore`WebCore::RenderBlock::layout() + 26 
    frame #20: 0x32b8b956 WebCore`WebCore::RenderBlock::layoutBlockChild(WebCore::RenderBox*, WebCore::RenderBlock::MarginInfo&, int&, int&) + 414 
    frame #21: 0x32b8b24c WebCore`WebCore::RenderBlock::layoutBlockChildren(bool, int&) + 428 
    frame #22: 0x32b8a1bc WebCore`WebCore::RenderBlock::layoutBlock(bool) + 704 
    frame #23: 0x32b897c2 WebCore`WebCore::RenderBlock::layout() + 26 
    frame #24: 0x32b8b956 WebCore`WebCore::RenderBlock::layoutBlockChild(WebCore::RenderBox*, WebCore::RenderBlock::MarginInfo&, int&, int&) + 414 
    frame #25: 0x32b8b24c WebCore`WebCore::RenderBlock::layoutBlockChildren(bool, int&) + 428 
    frame #26: 0x32b8a1bc WebCore`WebCore::RenderBlock::layoutBlock(bool) + 704 
    frame #27: 0x32b897c2 WebCore`WebCore::RenderBlock::layout() + 26 
    frame #28: 0x32b8974e WebCore`WebCore::RenderView::layout() + 334 
    frame #29: 0x32b85cba WebCore`WebCore::FrameView::layout(bool) + 1486 
    frame #30: 0x32b82c12 WebCore`WebCore::Document::implicitClose() + 794 
    frame #31: 0x32b828f6 WebCore`WebCore::FrameLoader::checkCallImplicitClose() + 86 
    frame #32: 0x32b827fe WebCore`WebCore::FrameLoader::checkCompleted() + 134 
    frame #33: 0x32b82380 WebCore`WebCore::FrameLoader::finishedParsing() + 64 

Screenshot of Leaks

UPDATE:与扩展的详细仪器。仍然没有指向源。它指向机器代码。

with Extended Detail

回答

1

如果您打开扩展详细视图,你应该能够看到调用堆栈当您选择从细节视图泄漏。另外,切换到调用树视图可以帮助您确定代码中发生泄漏的位置。使用跳转栏切换到呼叫树视图。

当您切换到调用树视图时,您应该在调用树的左侧看到一系列复选框。选择“反向调用树”和“隐藏系统库”复选框可以让您在调用树中查找代码。双击调用树中的一个函数将显示分配泄漏内存的代码行。

+0

谢谢。按照您的指示完成,但仍然没有指示我采取正确的方式。更新了问题。 – Raptor

+0

截图中的扩展细节视图显示了调用堆栈中的源代码。如果它只是显示机器码,你会得到调用堆栈中的内存地址而不是函数名称。调用树视图更适合查找您的代码。如果调用树视图显示内存地址而不是函数名称,请确保您的项目正在生成调试符号。 –