由于iPhone应用程序中的com.apple.locationd.registration.xpcq,启动超时崩溃(0x8badf00d)

时间:2011-10-07 08:43:38

标签: ios crash timeout watchdog

我在应用启动期间通过iTunes获得了一次奇怪的超时崩溃。这是堆栈跟踪。似乎与位置服务有关(是的,我确实要求用户的位置)。有没有人有这种崩溃的经历?

Thread 10 name:  Dispatch queue: com.apple.locationd.registration.xpcq
Thread 10:
0   libsystem_kernel.dylib          0x313dd2c8 semaphore_timedwait_trap
1   libdispatch.dylib               0x322db0e6 _dispatch_semaphore_wait_slow
2   libdispatch.dylib               0x322db154 dispatch_semaphore_wait$VARIANT$up
3   CoreLocation                    0x349cd838 CLClientInvokeCallback(__CLClient*, CLClientEvent, __CFDictionary const*)
4   CoreLocation                    0x349cffc0 ___CLClientCreateConnection_block_invoke_0
5   CoreLocation                    0x34a00c06 CLConnection::handleMessage(CLConnectionMessage*)
6   CoreLocation                    0x34a01a14 __setEventHandler_block_invoke_0
7   libxpc.dylib                    0x349c190a __XPC_CONNECTION_FAULT_BOUNDARY__
8   libxpc.dylib                    0x349badae _xpc_connection_recv_message
9   libxpc.dylib                    0x349bab5e _xpc_connection_wakeup_recv
10  libxpc.dylib                    0x349baa24 _xpc_connection_wakeup2
11  libxpc.dylib                    0x349ba462 _xpc_connection_wakeup
12  libdispatch.dylib               0x322dc21e _dispatch_source_invoke
13  libdispatch.dylib               0x322d9b70 _dispatch_queue_invoke$VARIANT$up
14  libdispatch.dylib               0x322d9caa _dispatch_queue_drain
15  libdispatch.dylib               0x322d9b66 _dispatch_queue_invoke$VARIANT$up
16  libdispatch.dylib               0x322d9caa _dispatch_queue_drain
17  libdispatch.dylib               0x322d9b66 _dispatch_queue_invoke$VARIANT$up
18  libdispatch.dylib               0x322da76c _dispatch_worker_thread2
19  libsystem_c.dylib               0x3351d4b0 _pthread_wqthread
20  libsystem_c.dylib               0x3351d384 start_wqthread

1 个答案:

答案 0 :(得分:1)

我有类似的问题。我通过完全重启我的iOS设备解决了这个问题。

我认为问题是远程调试服务器处于意外状态并导致应用程序中断正在运行的应用程序(我相信libxpc参与远程调试)。因此,清理它的最佳方法是简单地重新启动。