You should google EXC_GUARD, it’s interesting. 

0x40000002000000fe

the 02 in the middle says the guard is in dup(), which it is. The 0xfe at the 
end tells you what file descriptor it’s on. (0xfe .. really, seems unusually if 
not impossibly large for a file descriptor, you got that many files open?). 

That next bit 0x00007fa94044b9e0 is the magic number for that particular guard 
and how you decode that I have no idea. There’s a suggestion that may be a 
pointer/object reference.

So things which might cause this are using a file descriptor you gave to GCD to 
manage outside any context GCD gives it back to you to manage yourself. Using a 
close()d file descriptor which has then been re-openen by something else which 
‘guards’ it. I initially wondered if there was a block invoke on a block which 
had been released. Have you gone back to non-ARC again? 

Or it’s a framework bug. 

> On 5 Feb 2015, at 9:00 am, Graham Cox <graham....@bigpond.com> wrote:
> 
> Anyone seen this? My fault, or...?
> 
> OS Version:            Mac OS X 10.10.2 (14C109)
> Report Version:        11
> Anonymous UUID:        41C0442D-1002-83C7-8C29-1DCC8E683B2F
> 
> Sleep/Wake UUID:       5DE82D59-D0D8-4695-A86E-23F6ABBFAEAB
> 
> Time Awake Since Boot: 300000 seconds
> Time Since Wake:       6200 seconds
> 
> Crashed Thread:        7  Dispatch queue: 
> com.apple.networking.connection.0x7fa940613300
> 
> Exception Type:        EXC_GUARD
> Exception Codes:       0x40000002000000fe, 0x00007fa94044b9e0
> 
> 
> Thread 7 Crashed:: Dispatch queue: 
> com.apple.networking.connection.0x7fa940613300
> 0   libsystem_kernel.dylib            0x00007fff83900c1a dup + 10
> 1   libsystem_network.dylib           0x00007fff86cbb3d5 
> __tcp_connection_get_socket_block_invoke + 60
> 2   libdispatch.dylib                 0x00007fff896f1c13 
> _dispatch_client_callout + 8
> 3   libdispatch.dylib                 0x00007fff896f2e5e 
> _dispatch_barrier_sync_f_invoke + 57
> 4   libsystem_network.dylib           0x00007fff86cbb336 
> tcp_connection_get_socket + 135
> 5   com.apple.CFNetwork               0x00007fff8658e018 
> SocketStream::_onqueue_completeTCPConnection0(dispatch_data_s*) + 160
> 6   com.apple.CFNetwork               0x00007fff8658e786 
> ___ZN12SocketStream30_onqueue_completeTCPConnectionEv_block_invoke_2 + 129
> 7   libdispatch.dylib                 0x00007fff896f6323 
> _dispatch_call_block_and_release + 12
> 8   libdispatch.dylib                 0x00007fff896f1c13 
> _dispatch_client_callout + 8
> 9   libdispatch.dylib                 0x00007fff896f5365 
> _dispatch_queue_drain + 1100
> 10  libdispatch.dylib                 0x00007fff896f6ecc 
> _dispatch_queue_invoke + 202
> 11  libdispatch.dylib                 0x00007fff896f46b7 
> _dispatch_root_queue_drain + 463
> 12  libdispatch.dylib                 0x00007fff89702fe4 
> _dispatch_worker_thread3 + 91
> 13  libsystem_pthread.dylib           0x00007fff86028637 _pthread_wqthread + 
> 729
> 14  libsystem_pthread.dylib           0x00007fff8602640d start_wqthread + 13
> 
> 
> --Graham
> 


_______________________________________________

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to