My app died in _CG_spin_lock_try and I don't know what to make of this
My app died in _CG_spin_lock_try and I don't know what to make of this
- Subject: My app died in _CG_spin_lock_try and I don't know what to make of this
- From: Stuart Malin <email@hidden>
- Date: Wed, 11 Nov 2009 23:22:33 -0500
I'd appreciate some insight... alas, I don't have much good info... I
was running my app from Xcode... my app's window suddenly disappeared,
and GDB started up, so I opened the Debugger window. There was no
textual indication of why the app had died (that is, _no_ display of
something like EXEC_BAD_ACCESS).
Here's the stack trace back to my code, which (as you can see) invoked
-drawAtPoint on an NSImage.
#0 0x92d71b0d in _CG_spin_lock_try
#1 0x92d9c106 in CGAccessSessionCreate
#2 0x92d984ec in img_data_lock
#3 0x92d97329 in CGSImageDataLock
#4 0x9657e5e3 in ripc_AcquireImage
#5 0x9656c96d in ripc_DrawImage
#6 0x92d970fd in CGContextDrawImage
#7 0x9053dbff in -[NSCGImageRep drawInRect:]
#8 0x9053db63 in -[NSCGImageRep draw]
#9 0x90493ff9 in -[NSCachedImageRep draw]
#10 0x903e338c in -[NSImage drawInRect:fromRect:operation:fraction:]
#11 0x90480e37 in -[NSImage drawAtPoint:fromRect:operation:fraction:]
The assembler code for the the _CG_spin_lock_try method was the xchg
command in this dissassembly:
0x92d71b04 <+0000> mov 0x4(%esp),ìx
0x92d71b08 <+0004> mov $0x1010101,êx
0x92d71b0d <+0009> xchg êx,(ìx)
0x92d71b0f <+0011> xor $0x1010101,êx
0x92d71b14 <+0016> ret
0x92d71b15 <+0017> nopl (êx)
If there is anything useful that can be inferred from this that would
help me understand what happened (so I can try to recreate and debug),
I'd appreciate hearing. TIA.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden