Uli's Web Site
[ Zathras.de - Uli's Web Site ]
Other Sites: Stories
Abi 2000
Stargate: Resurgence
Lost? Site Map!
     home | blog | moose | programming | articles >> blog

 Blog Topics

15 Most Recent [RSS]

 Less work through Xcode and shell scripts
2011-12-16 @600
 iTunesCantComplain released
2011-10-28 @954
 Dennis Ritchie deceased
2011-10-13 @359
 Thank you, Steve.
2011-10-06 @374
 Cocoa Text System everywhere...
2011-03-27 @788
 Blog migration
2011-01-29 @520
 All you need to know about the Mac keyboard
2010-08-09 @488
 Review: Sherlock
2010-07-31 @978
 Playing with Objective C on Debian
2010-05-08 @456
 Fruit vs. Obst
2010-05-08 @439
 Mixed-language ambiguity
2010-04-15 @994
 Uli's 12:07 AM Law
2010-04-12 @881
 Uli's 1:24 AM Law
2010-04-12 @874
 Uli's 6:28 AM Law
2010-04-12 @869
 Uli's 3:57 PM Law
2010-04-12 @867


Uli's 11:06 PM Law

If you get weird crashes that look suspiciously like some other Cocoa class (that should really be holding on to an object of your class) is releasing your object prematurely, and thus an access to one of your instance variables causes a crash because that's already been freed, check what protocols your class's superclass conforms to. Chances are, it conforms to NSCopying, NSMutableCopying or NSCoding and you silly sleepwalker forgot to override copyWithZone: or mutableCopyWithZone:.

Sometimes this mindless mistake also looks as if there were somehow two copies of your object, one valid, and one for which there was never a constructor called, and which thus has some invalid instance variables and behaves zombie-like, but neither NSZombie nor any of your other memory debug tricks really trigger for it.

Reader Comments: (RSS Feed)
No comments yet
Or E-Mail Uli privately.

Created: 2007-09-17 @942 Last change: 2007-09-17 @833 | Home | Admin | Edit
© Copyright 2003-2023 by M. Uli Kusterer, all rights reserved.