Re: Return causes EXC_BAD_ACCESS
Re: Return causes EXC_BAD_ACCESS
- Subject: Re: Return causes EXC_BAD_ACCESS
- From: Dave DeLong <email@hidden>
- Date: Thu, 28 Jul 2011 15:01:31 -0700
Well, let's think about it. "Instance variables" are only accessible as long as you have an instance, right? You can't have an instance variable without an instance. So if you set "self" to nil... then you no longer have an instance. Thus, you cannot access self's instance variables, because there is no self.
Sorry I don't have a doc link for you; perhaps someone more well-versed with the documentation search tools than I can find something relevant. :)
Dave
On Jul 28, 2011, at 2:45 PM, Mr. Gecko wrote:
> That makes lots of sense, never even expected that to happen. Adding a local variable and setting it to the value before releasing it and returning that variable fixes the issue. I am still looking to an link to explanation in detail as to why this happens. If it's as I said, then I do not think I need it.
>
> On Jul 28, 2011, at 4:35 PM, Dave DeLong wrote:
>
>> It kind of looks like foundCookieJar is an ivar, which means that "return foundCookieJar" is really going to be "return self->foundCookieJar". Since you set "self" to "nil", you're trying to dereference a NULL pointer, which is a great way to crash your app.
>>
>> HTH,
>>
>> Dave
_______________________________________________
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