Re: [Xcode] Advanced EXC_BAD_ACCESS hunting
Re: [Xcode] Advanced EXC_BAD_ACCESS hunting
- Subject: Re: [Xcode] Advanced EXC_BAD_ACCESS hunting
- From: Alexander von Below <email@hidden>
- Date: Tue, 16 Feb 2010 17:17:35 +0100
Thanks for your reply!
Frist, some _very_ interesting news: If all I do is to change the URL to a WebDAV server (1), the error no longer occurs. When I change it back to the original (REST Service) URL, the error pops up again. I am completely perplexed. Framework bug?
But to your questions and suggestions:
Am 16.02.2010 um 16:45 schrieb Joar Wingfors:
> All of this still suggests some sort of memory management problem to me.
> That said, since the crash references some HTTP caching activity, perhaps you'd better clean out the web caches for your app?
I have unsuccessfully used NSURLReloadRequestIgnoringLocalAndRemoteCacheData. Any other things I should do?
> Is this using garbage collection or reference counting? I'd suggest being extra careful around the memory management of your connection delegates, and as a troubleshooting step perhaps sprinkling out some extra retain
Sorry, I forgot to say that I had already sprinkled retains generously around the code -- no change.
> One thing:
>
> Or even simpler:
>
> NSLog (%@, data);
Nice! I learn a new thing every day :D
Alex
1) I have witnesses! And the server even accepts the same username and password
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden