Re: double free and gdb problem
Re: double free and gdb problem
- Subject: Re: double free and gdb problem
- From: "Sean McBride" <email@hidden>
- Date: Fri, 20 Oct 2006 12:53:27 -0400
- Organization: Rogue Research
On 2006-10-20 18:16, Camille GOUREAU-SUIGNARD said:
>I'm still stuck with my double free location problem.
>Many thanks to Shawn for pointing me in the right direction.
>
>I had a look at this fabulous web page: http://www.cocoadev.com/
>index.pl?DebuggingAutorelease
>I set the environment variables, but I nver get the message giving me
>the memory address (the one I'll use in Malloc_history) in the console:
>
>What I should get:
>2003-03-18 13:01:38.644 autoreleasebug[3939] *** *** Selector 'release'
> sent to dealloced instance 0xa4e10 of class NSConcreteData.
>
>What I get:
>2006-10-20 18:12:14.159 Caisse enregistreuse[18291] ticket a change
>Program received signal: "EXC_BAD_ACCESS".
>
>Any idea on how to get that message ?
That is indeed a very nice article. Though I'm a bit surprised it
works, because my understanding is that NSZombie is only useful for non-
toll free bridged classes. And NSData is toll free bridged.
Nevertheless, I tried what the article says and it works.
However, if you change his example to use NSString instead of NSData
then you do not catch the problem. But if you add in CFZombieLevel,
then you can catch the problem. If you are not familiar with
CFZombieLevel, do read up on it, it has been discussed on Apple lists in
the past.
--
____________________________________________________________
Sean McBride, B. Eng email@hidden
Rogue Research www.rogue-research.com
Mac Software Developer Montréal, Québec, Canada
_______________________________________________
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