Re: objc_msgSend() selector name: tableView:objectValueForTableColumn:row:

2015-09-03 Thread Raglan T. Tiger
t;> >>>> 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? >

Re: objc_msgSend() selector name: tableView:objectValueForTableColumn:row:

2015-09-03 Thread Raglan T. Tiger
es 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? >>> >>>

Re: objc_msgSend() selector name: tableView:objectValueForTableColumn:row:

2015-05-27 Thread Charles Srstka
> On May 27, 2015, at 10:22 AM, Kyle Sluder wrote: > >> On May 27, 2015, at 8:17 AM, Scott Ribe > > wrote: > >> >>> On May 27, 2015, at 8:20 AM, Kyle Sluder >> > wrote: >>> >>> The bug is in your code. It has always been a requiremen

Re: objc_msgSend() selector name: tableView:objectValueForTableColumn:row:

2015-05-27 Thread Scott Ribe
On May 27, 2015, at 8:20 AM, Kyle Sluder wrote: > > The bug is in your code. It has always been a requirement that you nil out > any delegate and datasource backpointers before the thing they point to gets > deallocated. You just happened to get away with it due to some aspect of > older Xcode

Re: objc_msgSend() selector name: tableView:objectValueForTableColumn:row:

2015-05-27 Thread Kyle Sluder
> On May 27, 2015, at 8:17 AM, Scott Ribe wrote: > >> On May 27, 2015, at 8:20 AM, Kyle Sluder wrote: >> >> The bug is in your code. It has always been a requirement that you nil out >> any delegate and datasource backpointers before the thing they point to gets >> deallocated. You just happ

Re: objc_msgSend() selector name: tableView:objectValueForTableColumn:row:

2015-05-27 Thread Kyle Sluder
> On Apr 13, 2015, at 12:11 PM, Raglan T. Tiger wrote: > > Just a quick follow-up and thanks to those that put me on the right path. > > I ran the code in GDB on a 10.6.8 machine and set NSZombieEnabled=YES. This > showed me the object that was released that Cocoa was calling > tableView:obje

Re: objc_msgSend() selector name: tableView:objectValueForTableColumn:row:

2015-05-26 Thread Charles Srstka
On May 26, 2015, at 7:23 PM, Raglan T. Tiger wrote: > > My solution to this problem was to set the tableview delegate to nil in the > windowwillclose for the window containing the table. > > My code now runs 10.5 and upward, built with 10.9 sdk on Xcode 6.2 > > -rags I was getting the crash w

Re: objc_msgSend() selector name: tableView:objectValueForTableColumn:row:

2015-05-26 Thread Scott Ribe
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:objectValue

Re: objc_msgSend() selector name: tableView:objectValueForTableColumn:row:

2015-04-13 Thread Raglan T. Tiger
Just a quick follow-up and thanks to those that put me on the right path. I ran the code in GDB on a 10.6.8 machine and set NSZombieEnabled=YES. This showed me the object that was released that Cocoa was calling tableView:objectValueForTableColumn:row: on after release. This was only a proble

Re: objc_msgSend() selector name: tableView:objectValueForTableColumn:row:

2015-04-09 Thread Raglan T. Tiger
-rags > On Apr 9, 2015, at 12:22 PM, Jens Alfke wrote: > > Use NSZombieEnabled Isn't this for use within Xcode? I am running the app on a 10.6.8 machine , not from Xcode on that machine. -rags ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.

Re: objc_msgSend() selector name: tableView:objectValueForTableColumn:row:

2015-04-09 Thread Jens Alfke
Use NSZombieEnabled. Looking at registers isn’t going to help you because the offending memory address probably isn’t a pointer to the object (most likely it’s some bogus address found at the location where the deceased object’s ‘isa’ pointer used to be.) —Jens _

Re: objc_msgSend() selector name: tableView:objectValueForTableColumn:row:

2015-04-09 Thread Charles Srstka
o 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 o

objc_msgSend() selector name: tableView:objectValueForTableColumn:row:

2015-04-09 Thread Raglan T. Tiger
nce 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: