Re: EXC_BAD_ACCESS in _class_changeInfo
Re: EXC_BAD_ACCESS in _class_changeInfo
- Subject: Re: EXC_BAD_ACCESS in _class_changeInfo
- From: Dave DeLong <email@hidden>
- Date: Fri, 06 Mar 2009 10:04:37 -0700
After some rather indepth testing, I found out that I hadn't declared
the static arrays correctly (sigh...). Fixing the declarations fixed
the crashing problem, but led to other ones (unrelated, I think). I
was eventually able to fix it.
Dave
On Mar 3, 2009, at 9:04 AM, Greg Parker wrote:
Most likely, you've sent a message to an invalid object, or to a
valid object that was mangled by a memory error elsewhere. Usually
that will crash inside objc_msgSend() itself, but if your bogus
object happens to include dereferenceable pointers in the right
places then the Objective-C runtime will happily traverse the
"object" and "isa" and "method cache" and "class info" and finally
fall over somewhere like the +initialize machinery as seen here.
Debug it as if it had crashed in objc_msgSend() itself. Make sure
the memory management of the receiver is good, and if it is then
look for other memory errors that might have clobbered it. NSZombie
and Guard Malloc are probably your new best friends.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden