Re: objc_msgSend() selector name: tableView:objectValueForTableColumn:row:
Re: objc_msgSend() selector name: tableView:objectValueForTableColumn:row:
- Subject: Re: objc_msgSend() selector name: tableView:objectValueForTableColumn:row:
- From: Scott Ribe <email@hidden>
- Date: Tue, 26 May 2015 18:17:00 -0600
On Apr 9, 2015, at 12:17 PM, Charles Srstka <email@hidden> wrote:
>
>> On Apr 9, 2015, at 12:41 PM, Raglan T. Tiger <email@hidden> wrote:
>>
>> My app runs just fine on OS X version > 10.6.8.
>>
>> On 10.6.8 it crashes.
>>
>> The crash report indicates a bad object having called on it tableView:objectValueForTableColumn:row:
>>
>> The eax register has a value that does not match any table being used in the app.
>>
>> The call stack does not show reference to the app.
>>
>> I have attempted to symbolicate this using atos but no results.
>>
>> What is an appropriate methodology to determine the offending entry in the eax register?
>>
>> ========================
>> Application Specific Information:
>> objc_msgSend() selector name: tableView:objectValueForTableColumn:row:
>>
>>
>> Thread 0 Crashed: Dispatch queue: com.apple.main-thread
>> 0 libobjc.A.dylib 0x92f43f94 objc_msgSend + 36
>> 1 com.apple.AppKit 0x9179a1da -[NSTableView preparedCellAtColumn:row:] + 335
>> 2 com.apple.AppKit 0x917b46bc -[NSTableView _drawContentsAtRow:column:withCellFrame:] + 56
...
>> 27 com.apple.AppKit 0x9168c289 NSApplicationMain + 574
>> 28 com.britonleap.Embrilliance 0x0001d938 main + 824
>> 29 com.britonleap.Embrilliance 0x00002985 start + 53
>> ==============================
>
> I had this same problem when I was still planning to make Pacifist 3.5 compatible with 10.6.x. What I found was that if I compiled the same code with Xcode 5.x, it would work, but that Xcode 6 had some sort of problem compiling code that would work on Snow Leopard without getting that same crash in the NSTableView code. So basically your options are to downgrade to an older version of Xcode (which might mean downgrading your OS X installation as well, since I don’t know if Xcode 5 can run on Yosemite), or drop 10.6 support. My decision was to do the latter; Snow Leopard is four years old now. Time to move on.
Well now, if this isn’t totally strange. I’m starting to see this problem *after* switching to Xcode 6.2 and switching my base SDK (& deployment target) from 10.8 to 10.9.
Either of you ever figure out anything more about this?
--
Scott Ribe
email@hidden
http://www.elevated-dev.com/
https://www.linkedin.com/in/scottribe/
(303) 722-0567 voice
_______________________________________________
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