AppStore的基础上的iPhone 3G和iPod Touch上推出崩溃 [英] AppStore build crashes on launch on iPhone 3g and iPod Touch
问题描述
看着计算器和许多其他论坛后，决定要问这个问题。该来讨论确切的问题我最近的是<一个href=\"http://stackoverflow.com/questions/1282428/whats-the-difference-between-kern-invalid-address-and-kern-protection-failure/1282473#1282473\">this回答
After looking at stackoverflow and many other forums, decided to ask this question. The closest that came to discussing the exact problem I have is this answer
我有一个应用程序在AppStore多数民众赞成建在一个相当稳定的codeBase的，并一直沿用过去的两年。但现在，提交最近更新的应用程序后，其对iPhone 3G的崩溃（4.2.1版本）。它不会在设备上崩溃当我运行调试版本
I have an App in the AppStore thats been built on a fairly stable codebase and has been in use for the past two years. But now, after submitting a recent update to the app, its crashing on iPhone 3G (version 4.2.1). It doesn't crash on the device when I run a debug build
下面是基于其他职位我已经验证点：
Here are the points I have verified based on other posts:
- 所有生成配置（调试/分销/ AppStore的），已经被设置为最低版本为3.0，SDK基地，以最新的
- 有效架构值设置为ARMv6的ARMv7的
- 我没有得到一个吃badfood异常（异常code：0x8badf00d）
- 它适用于大多数较新的iOS设备，我可以测试它
- 构建有源体系不仅是检查
- 推出的5秒内的应用程序崩溃，所以它不是看门狗，推出搞乱
- 二进制使用内置X $ C $ç3.2.6
- Symbolicated Crashlogs不要对他们有很多信息，我能够理解
下面是崩溃日志
Date/Time: 2011-07-01 11:16:06.728 -0400
OS Version: iPhone OS 4.2.1 (8C148)
Report Version: 104
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0048af00
Crashed Thread: 0
Thread 0 Crashed:
0 ??? 0x0048af00 0 + 4763392
Thread 1:
0 libSystem.B.dylib 0x35d8f974 kevent + 24
1 libSystem.B.dylib 0x35e5e2fc _dispatch_mgr_invoke + 88
2 libSystem.B.dylib 0x35e5dd68 _dispatch_queue_invoke + 96
3 libSystem.B.dylib 0x35e5d788 _dispatch_worker_thread2 + 120
4 libSystem.B.dylib 0x35de6970 _pthread_wqthread + 392
5 libSystem.B.dylib 0x35ddd2fc start_wqthread + 0
Thread 2:
0 libSystem.B.dylib 0x35de454c __semwait_signal + 24
1 libSystem.B.dylib 0x35d90f70 _pthread_cond_wait + 1140
2 libSystem.B.dylib 0x35d90910 pthread_cond_wait + 48
3 Foundation 0x3517ed5e -[NSCondition wait] + 170
4 Foundation 0x35169106 -[NSObject(NSThreadPerformAdditions) performSelector:onThread:withObject:waitUntilDone:modes:] + 764
5 Foundation 0x35168d5e -[NSObject(NSThreadPerformAdditions) performSelectorOnMainThread:withObject:waitUntilDone:] + 98
6 MyCrashingApp 0x00014ab0 -[URLDownload connectionDidFinishLoading:] (URLDownload.m:79)
7 Foundation 0x35184232 -[NSURLConnection(NSURLConnectionReallyInternal) sendDidFinishLoading] + 62
8 Foundation 0x351841b4 _NSURLConnectionDidFinishLoading + 72
9 CFNetwork 0x302957e0 URLConnectionClient::_clientDidFinishLoading(URLConnectionClient::ClientConnectionEventQueue*) + 212
10 CFNetwork 0x30284b00 URLConnectionClient::ClientConnectionEventQueue::processAllEventsAndConsumePayload(XConnectionEventInfo<XClientEvent, XClientEventParams>*, long) + 132
11 CFNetwork 0x30284d7c URLConnectionClient::ClientConnectionEventQueue::processAllEventsAndConsumePayload(XConnectionEventInfo<XClientEvent, XClientEventParams>*, long) + 768
12 CFNetwork 0x3028497c URLConnectionClient::processEvents() + 92
13 CFNetwork 0x30284844 MultiplexerSource::perform() + 184
14 CFNetwork 0x30284780 MultiplexerSource::_perform(void*) + 4
15 CoreFoundation 0x375518ca __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 8
16 CoreFoundation 0x37521ec6 __CFRunLoopDoSources0 + 378
17 CoreFoundation 0x375216f2 __CFRunLoopRun + 258
18 CoreFoundation 0x37521504 CFRunLoopRunSpecific + 220
19 CoreFoundation 0x37521412 CFRunLoopRunInMode + 54
20 Foundation 0x35156238 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 200
21 Foundation 0x351d52ea -[NSRunLoop(NSRunLoop) runUntilDate:] + 62
22 MyCrashingApp 0x000148a4 -[URLDownload startDownload:] (URLDownload.m:57)
23 CoreFoundation 0x375466fc __invoking___ + 60
24 CoreFoundation 0x375465d6 -[NSInvocation invoke] + 110
25 Foundation 0x351cd8fe -[NSInvocationOperation main] + 78
26 Foundation 0x3516054a -[__NSOperationInternal start] + 658
27 Foundation 0x351602a8 -[NSOperation start] + 16
28 Foundation 0x35174b8c ____startOperations_block_invoke_2 + 40
29 libSystem.B.dylib 0x35e5d268 _dispatch_call_block_and_release + 12
30 libSystem.B.dylib 0x35e5d788 _dispatch_worker_thread2 + 120
31 libSystem.B.dylib 0x35de6970 _pthread_wqthread + 392
32 libSystem.B.dylib 0x35ddd2fc start_wqthread + 0
Thread 3:
0 libSystem.B.dylib 0x35d5b40c semaphore_wait_signal_trap + 8
1 libSystem.B.dylib 0x35d91448 semaphore_wait_signal + 4
2 libSystem.B.dylib 0x35d5d4ec pthread_mutex_lock + 376
3 WebCore 0x330777c4 _WebTryThreadLock(bool) + 44
4 WebCore 0x33077e5c WebRunLoopLock(__CFRunLoopObserver*, unsigned long, void*) + 28
5 CoreFoundation 0x3752a808 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 12
6 CoreFoundation 0x3752a636 __CFRunLoopDoObservers + 494
7 CoreFoundation 0x375219a2 __CFRunLoopRun + 946
8 CoreFoundation 0x37521504 CFRunLoopRunSpecific + 220
9 CoreFoundation 0x37521412 CFRunLoopRunInMode + 54
10 WebCore 0x3318bd14 RunWebThread(void*) + 524
11 libSystem.B.dylib 0x35de5b44 _pthread_start + 364
12 libSystem.B.dylib 0x35dd77a4 thread_start + 0
Thread 4:
0 libSystem.B.dylib 0x35de72fc __workq_kernreturn + 8
1 libSystem.B.dylib 0x35de6b50 _pthread_wqthread + 872
2 libSystem.B.dylib 0x35ddd2fc start_wqthread + 0
Thread 5:
0 libSystem.B.dylib 0x35d5b3b0 mach_msg_trap + 20
1 libSystem.B.dylib 0x35d5d894 mach_msg + 60
2 CoreFoundation 0x37521f7c __CFRunLoopServiceMachPort + 88
3 CoreFoundation 0x37521780 __CFRunLoopRun + 400
4 CoreFoundation 0x37521504 CFRunLoopRunSpecific + 220
5 CoreFoundation 0x37521412 CFRunLoopRunInMode + 54
6 Foundation 0x3517ec4e +[NSURLConnection(NSURLConnectionReallyInternal) _resourceLoadLoop:] + 210
7 Foundation 0x3515cb8a -[NSThread main] + 42
8 Foundation 0x35155b90 __NSThread__main__ + 908
9 libSystem.B.dylib 0x35de5b44 _pthread_start + 364
10 libSystem.B.dylib 0x35dd77a4 thread_start + 0
Thread 6:
0 libSystem.B.dylib 0x35d848d8 select$DARWIN_EXTSN + 20
1 CoreFoundation 0x3755aa34 __CFSocketManager + 356
2 libSystem.B.dylib 0x35de5b44 _pthread_start + 364
3 libSystem.B.dylib 0x35dd77a4 thread_start + 0
Thread 0 crashed with ARM Thread State:
r0: 0x00000000 r1: 0x00000000 r2: 0x3e73eb48 r3: 0x00000000
r4: 0x0048aba0 r5: 0x00000000 r6: 0x3e73eaa8 r7: 0x0048aba0
r8: 0x0048af00 r9: 0x3e25d978 r10: 0x35ce9029 r11: 0x0048af00
ip: 0x3e6a4c58 sp: 0x2fdfe298 lr: 0x3596ed90 pc: 0x0048af00
cpsr: 0x40070010
任何答案，即使他们只是点我朝着正确的方向是AP preciated。
Any answers, even if they just point me in the right direction are appreciated.
推荐答案
因此，这里就是帮助解决这个问题。我希望它可以帮助别人了。
So here's what helped solve this problem. I hope it helps others too.
在AppStore构建我用X code 3.2.6创建
The AppStore build I created was using Xcode 3.2.6
显然有一些问题，X code'S 的连接器作为去年。 <一href=\"http://www.dizzey.com/development/ios/duplicate-symbols-when-linking-objectivec-static-libraries/\"相对=nofollow>我-all_load标记错误周围试图一塌糊涂的时候迷迷糊糊的这个。
Apparently there's some problem with XCode's linker as of last year. I stumbled in to this when trying to mess around with -all_load flag errors.
现在，当我创建一个使用X code4相同的构建（没有code修改，没有设置更改）时，即席版本不会崩溃。
Now, when I create the same build (no code change, no settings changes) using XCode4, the adhoc version doesn't crash.
有关我现在这个版本的更新在AppStore版本。如果有人读这个答案想知道后面的X $ C $的C这种行为的技术推理，请不要发表您的答案。它会帮助节省headBangingAgainstTheWall多小时！
For now I am updating the appStore version with this build. If anyone reading this answer thinks knows the technical reasoning behind this behavior of XCode, please do post your answer. It'll help save many hours of headBangingAgainstTheWall!
使用以下关键字的谷歌搜索帮助：搜索
-all_load崩溃结果
RNBRunLoopLaunchInferior（这显示了在控制台中，当应用程序崩溃并打印 RNBRunLoopLaunchInferior DNBProcessLaunch（）返回的错误：DRHT）
using the following keywords for googling helped:
"-all_load" crashes
RNBRunLoopLaunchInferior (this showed up in the console when the app crashed and printed RNBRunLoopLaunchInferior DNBProcessLaunch() returned error: 'DRHT')
希望这有助于！
这篇关于AppStore的基础上的iPhone 3G和iPod Touch上推出崩溃的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
