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

Correction set the delegate and datasource to nil. -rags > On May 26, 2015, at 6: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 wi

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

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 > On May 26, 2015, at 6:17 PM, Scott Ribe wrote: > > On Apr 9, 2015, at 12:17 PM, Charles S

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

> 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:

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:

> 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:

> 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:

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:

On Apr 9, 2015, at 12:17 PM, Charles Srstka wrote: > >> On Apr 9, 2015, at 12:41 PM, Raglan T. Tiger 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:objectValueForTableColu

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

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:

-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:

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:

> On Apr 9, 2015, at 12:41 PM, Raglan T. Tiger 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 a

Re: objc_msgSend

First, see the documentation for +[NSObject initialize] (a class method) to learn what that method is and does. Second, the crash report indicates infinite recursion and eventual exhaustion of the stack or heap. Third, when something like this only happens to one customer out of hundreds, I of

Re: objc_msgSend

the crash report is here http://highrolls.net/objc_msgSend On Jun 21, 2010, at 9:27 AM, k...@highrolls.net wrote: I understand that a crash in objc_msgSend is related calling a method on a released / nil object. The linked Crash Report , from a customer, seems strange to me as it shows t

Re: objc_msgSend() tour

On 4 Feb 2010, at 06:58, Bill Bumgarner wrote: > Folks- > > I finally banged out part IV -- the 'slow path' & odds/ends -- of my > tour of objc_msgSend() on x86_64. If you want to know how method invocations > works in instruction by instruction detail on x86_64, you might find it > int