ansaurus

Question

NSString and UITouch...what in the world is going on?

Answer 1

+1 A:

A likely cause for problems like these is that "conversions" got released too early, thus got deallocated and you were still holding a reference to that memory location. Then another object got allocated at this location.

To debug this, set NSZombieEnabled. It doesn't deallocate objects but replaces them with "zombies". See for example the following link:

http://www.tomwhitson.co.uk/blog/2009/04/debugging-with-nszombiesenabled/

DarkDust 2010-08-09 14:59:18

This seems to be the problem. Why would it have been released too early and how do I prevent that from happening?

Robert Eisinger 2010-08-09 15:08:05

Well obviously you either called [conversions release] or [conversions autorelease] too often or you called [conversions retain] to few :-) Without context I can't tell. But have a look at this:http://blog.mikeweller.com/2009/07/retain-and-release-rules-in-objective-c.html

DarkDust 2010-08-09 15:16:24

Another good link is this one here on Stack Overflow:http://stackoverflow.com/questions/6578/understanding-reference-counting-with-cocoa-objective-c

DarkDust 2010-08-09 15:26:48

I never called conversions release or autorelease except for a release call in the dealloc method. I'm not familiar with retain. When declaring the string in the .h file, I make it a property with a nonatomic, retain property. Is this not enough?

Robert Eisinger 2010-08-09 16:45:16

Then you need to use property assignment: `self.conversions = ...`

tc. 2010-08-09 19:02:19

ansaurus

tags:

views:

answers:

NSString and UITouch...what in the world is going on?

related questions