我完全无法跟踪问题.它在iOS 4上运行良好,但我猜这只是因为它更容忍错误或某些东西.我已经尝试在各处设置断点,逐步通过,在“僵尸”配置文件中的“仪器”中运行它,但它只是炸d而不告诉我哪里.我没有警告和干净的分析,所以我有点失望,看看下一个.任何人都可以提供任何建议?谢谢.
回溯是:
(gdb) backtrace#0 0x024fb939 in _dispatch_retain ()#1 0x024fbc02 in dispatch_source_cancel ()#2 0x0109e492 in _CFURLCacheDeallocate ()#3 0x0205a4e3 in CFRelease ()#4 0x010331b1 in httpProtocol::~httpProtocol ()#5 0x0100c75d in CFClass::FinalizeObj ()#6 0x0205a4e3 in CFRelease ()#7 0x02110af0 in __CFDictionaryStandardReleaseValue ()#8 0x020714b1 in __CFBasicHashDrain ()#9 0x0205a4e3 in CFRelease ()#10 0x01024237 in SocketStream::~SocketStream ()#11 0x0100c75d in CFClass::FinalizeObj ()#12 0x0205a4e3 in CFRelease ()#13 0x01023e0b in SocketStream::finalize ()#14 0x01023dc6 in virtual thunk to SocketStream::finalize(voID const*) ()#15 0x01023da1 in ReadStreamCallbacks::_finalize ()#16 0x0208201a in __CFStreamDeallocate ()#17 0x0205a4e3 in CFRelease ()#18 0x01030a6c in httpReadFilter::~httpReadFilter ()#19 0x0100c75d in CFClass::FinalizeObj ()#20 0x0205a4e3 in CFRelease ()#21 0x010c22bc in non-virtual thunk to httpReadFilter::readStreamFinalize(__CFReadStream*) ()#22 0x0102ff1c in CFNetworkReadStream::httpStreamFinalize ()#23 0x0208201a in __CFStreamDeallocate ()#24 0x0205a4e3 in CFRelease ()#25 0x0103070f in NetConnection::shutdownConnectionStreams ()#26 0x010bf1fc in NetConnection::closeStreamsIfPossibleOrSignalThatThatNeedsTobedonePrettyPlease ()#27 0x0103485b in httpconnectionCacheEntry::removeUnauthConnection ()#28 0x010d6d2d in httpconnectionCacheEntry::purgeIDleConnections ()#29 0x010d3c1e in ConnectionCacheTLS::resetCacheForThisThread ()#30 0x0101b739 in ConnectionTimerTLS::_timerPurgeEntrIEs ()#31 0x02122966 in __CFRUNLOOP_IS_CALliNG_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ ()#32 0x02122407 in __CFRunLoopDoTimer ()#33 0x020857c0 in __CFRunLoopRun ()#34 0x02084db4 in CFRunLoopRunspecific ()#35 0x02084ccb in CFRunLoopRunInMode ()#36 0x00206e40 in +[NSURLConnection(Loader) _resourceLoadLoop:] ()#37 0x001184e6 in -[NSThread main] ()#38 0x00118457 in __NSThread__main__ ()#39 0x98d6b259 in _pthread_start ()#40 0x98d6b0de in thread_start ()解决方法 在调试器中设置 NSZombieEnabled,MallocStackLogging和 guard malloc.然后,当您的App崩溃时,在gdb控制台中键入:
(gdb) info malloc-history 0x543216
将0x543216替换为导致崩溃的对象的地址,并且您将获得更有用的堆栈跟踪,并且它可以帮助您精确定位导致问题的代码中的确切行.
See this article for more detailed instructions.
总结以上是内存溢出为你收集整理的iphone – “Thread 6 com.apple.NSURLConnectionLoader:程序接收信号:EXC_BAD_ACCESS”全部内容,希望文章能够帮你解决iphone – “Thread 6 com.apple.NSURLConnectionLoader:程序接收信号:EXC_BAD_ACCESS”所遇到的程序开发问题。
如果觉得内存溢出网站内容还不错,欢迎将内存溢出网站推荐给程序员好友。
欢迎分享,转载请注明来源:内存溢出
评论列表(0条)