Re: Weird crashes on Yosemite
Re: Weird crashes on Yosemite
- Subject: Re: Weird crashes on Yosemite
- From: Steve Mills <email@hidden>
- Date: Fri, 13 Mar 2015 09:55:19 -0500
On Mar 13, 2015, at 09:46:36, Peter Hudson <email@hidden> wrote:
> Crashed Thread: 0 Dispatch queue: com.apple.main-thread
>
> Exception Type: EXC_BAD_ACCESS (SIGSEGV)
> Exception Codes: KERN_INVALID_ADDRESS at 0x00000000ffffffff
>
> objc_msgSend() selector name: objectAtIndex:
>
> Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
> 0 libobjc.A.dylib 0x938810ab objc_msgSend + 27
> 1 com.apple.AppKit 0x9184a305 -[NSTableView _dataSourceValueForColumn:row:] + 69
> 2 com.apple.AppKit 0x9194e127 -[NSTableView preparedCellAtColumn:row:] + 385
> 3 com.apple.AppKit 0x917efc91 -[NSTableView _dirtyVisibleCellsForKeyStateChange] + 878
What do you have set as the dataSource for the table? Is it still valid when the window owning the table becomes key? Is it owned by some object that might be in a weak property instead of strong? (Although you would probably see that right away when you debugged it.) Have you run static analysis on the project? Have you turned on Scribble, Guard Edges, and Guard Malloc in your scheme while debugging? Some of those can sometimes help force bugs to the surface.
--
Steve Mills
Drummer, Mac geek
_______________________________________________
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