On 1/21/19 10:07 AM, Quincey Morris wrote:
On Jan 21, 2019, at 09:39 , James Walker <jam...@frameforge3d.com
<mailto:jam...@frameforge3d.com>> wrote:
I used LLDB, and said
env NSZombieEnabled=YES
before starting the process.
You should turn on zombies from the Diagnostics panel of your target’s
scheme, or (as Ken suggested) use Instruments.
I tried the Zombies instrument, and the backtrace looks a little
different I can see that there's a notification involved. Does the
__dealloc_zombie mean I've got a double free?
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 ??? 0x00000001180b35e6 0 + 4698355174
1 com.apple.CoreFoundation 0x00007fff86c31350
-[NSObject(NSObject) __dealloc_zombie] + 64
2 ??? 0x000000010ddba6d9 0 + 4527466201
3 liboainject.dylib 0x0000000110875147
___swapMethods_block_invoke_4 + 272
4 ??? 0x000000010ddbb044 0 + 4527468612
5 ??? 0x000000010d438703 0 + 4517496579
6 com.apple.CoreFoundation 0x00007fff86bfce0c
__CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12
7 com.apple.CoreFoundation 0x00007fff86af082d
_CFXNotificationPost + 2893
8 com.apple.Foundation 0x00007fff8dcb4dda
-[NSNotificationCenter postNotificationName:object:userInfo:] + 68
9 com.apple.AppKit 0x00007fff871ae304 -[NSApplication
terminate:] + 1604
The backtrace doesn't show any of my code, …
Er, it sure looks like it does:
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 ??? 0x000000010c3013e6 0 + 4499444710
…
17 com.apple.AppKit 0x00007fff93342783 NSApplicationMain + 940
18 ??? 0x00000001034e3f10 0 + 4350426896
19 ??? 0x0000000102e3e034 0 + 4343455796
Lines 0, 18 and 19 look like locations in your code, unsymbolicated.
…so I'm not sure how to proceed
You could try symbolicating the crash log.
The usual way I symbolicate a crash log, using atos, isn't working in
this case. But I am seeing some symbols when I crash under lldb. So now
I have a few clues to work with. Thanks, everyone.
3 com.apple.AppKit 0x00007fff93355e79 -[NSApplication windows] + 17
…
6 com.apple.AppKit 0x00007fff935d7347 -[NSApplication terminate:] + 1671
So, your application appears to be terminating, and as part of that
process something seems to be happening with windows, likely closing of
windows. It’s extremely easy to get into an order-of-deallocation
problem with views, view controllers, delegates and other objects,
leading to a dangling pointer to an unallocated object. It’s also
extremely for common that the timing differs by macOS version, which
means it might crash in some versions, not in others.
_______________________________________________
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
