Re: Breaking into debugger after program hangs....

FROM : John Draper
DATE : Thu Apr 28 22:43:09 2005

Nick Zitzmann wrote:

>
> On Apr 28, 2005, at 4:40 AM, Ondra Cada wrote:
>

>> Does not feel right, the problem would be elsewhere. If zombies 
>> enabled, the program does not crash this way. It would report what 
>> happened.

>
>
> ...unless the object was an NSString, NSArray, NSNumber, 
> NSDictionary, NSSet, or some other object that is toll-free bridged 
> to a CoreFoundation object.


I never DID understand this "Toll free" concept....  can someone come
forward and explain
this?    Isn't this just a kind of "wrapper" around the lower level
Carbon Procedural calls?

Well - then perhaps I was wrong in how I enabled Zombies,  because I
just followed the
instructions in the Tech Note....  It clearly says I just select the
Target (Executeable)
and go to File --> Show Inspector --> Arguments (tab) --> and put in the
"NSZombieEnabled = YES"
Is that right?  If so,  then my program is NOT reporting what
happened....  Do I need to
issue some "secret" command to "gdb" to get this info?

And as of yet - nobody came forward to tell me how I can "break" out of
a "Hang" and
get back into the debugger....  isn't there ANYONE out on this list
that knows?
And where are these APPLE PEOPLE I heard about who actually read this
list... 
Can't any of you please answer this?

> Those objects don't become zombies even  if NSZombieEnabled is
> enabled, so the program will crash if they are  accessed after being
> deallocated.


So - what you are saying,  is that this variable will NOT help me?    It
DID make somewhat
of a difference...  It caused the BAD_EXEC error?  but it don't cause
it every time,  and
when I remove it,  I don't get this error at all,  I just get it
hanging up.....Now if I can
figure out how to break out of this...

John