Also, Xcode's built-in "Analyze" menu item might catch some of those.
Cheers,
-- Uli Kusterer
"The Witnesses of TeachText are everywhere..."
http://www.zathras.de
On Feb 13, 2013, at 10:36 PM, Sean McBride wrote:
> On Wed, 13 Feb 2013 19:50:29 +0800, anni saini said:
>
>> Can anybody know how
On Wed, 13 Feb 2013 19:50:29 +0800, anni saini said:
>Can anybody know how to resolve the issue of "Pointer was being free
>was not allocated" I was facing this issue with my project on 10.7 and
>10.8 however the code works perfectly fine on 10.6. Any idea what is
>causing this?
There are lots o
On Feb 13, 2013, at 4:50 AM, anni saini wrote:
> Can anybody know how to resolve the issue of "Pointer was being free was not
> allocated" I was facing this issue with my project on 10.7 and 10.8 however
> the code works perfectly fine on 10.6. Any idea what is causing this?
You're probably fr
Sounds like a classic memory management error. Either you are using a pointer
to an object after you've released it, or you are keeping an autoreleased
pointer beyond the lifetime of the current autorelease pool without retaining
it, or a pointer to an object inside an NSArray or NSDictionary af
