Re: [SOLVED] Crash when creating instance of class

FROM : Jason Bell
DATE : Tue Nov 23 20:20:26 2004

Another example of what can happen after several long nights working on
an overdue project.

If anyone is curious, this is what will happen if you try to
instantiate a class when you've excluded the definition of its
superclass from the target.  Oops.

- Jason


On Nov 23, 2004, at 12:35 PM, Jason Bell wrote:

> I've been doing Cocoa development for quite a while now and for the
> first time, I've encountered a problem where I have absolutely no clue
> what to even try next.
>
> My application crashes with an EXC_BAD_ACCESS when attempting to
> create an instance of one of my classes.  Specifically, the problem
> occurs in this code:
>
> AIPerson *person;
> person = [[AIPerson alloc] init];
>
> Pretty simple, right?  We all do it millions of times.  Well, the
> second line produces a crash log with this:
>
> Exception:  EXC_BAD_ACCESS (0x0001)
> Codes:      KERN_PROTECTION_FAILURE (0x0002) at 0x00000010
>
> Thread 0 Crashed:
> 0  libobjc.A.dylib               0x9083293c class_initialize + 0x9c
> 1  libobjc.A.dylib               0x9083294c class_initialize + 0xac
> 2  libobjc.A.dylib               0x90831524
> _class_lookupMethodAndLoadCache + 0x84
> 3  libobjc.A.dylib               0x90831298 objc_msgSend + 0xb8
> ......
>
> It doesn't even get to the init method.  I don't have my own
> +(void)initialize method and if I add one, it doesn't get run either. 
> I've tried a clean-rebuild and even deleting the entire build folder. 
> Since I get no compile-time errors or warnings and this log is all I
> have to go on, I'm at a bit of a loss.
>
> Seems strange, I know.  I just can't think of a way to make this
> happen even if I wanted it to.  Any suggestions?
>
> - Jason Bell
>