• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Debug Help
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Debug Help


  • Subject: Re: Debug Help
  • From: email@hidden
  • Date: Mon, 16 Dec 2002 17:27:54 -0600

Thanks for the reply Mike.

When I break on main and type 'p NSZombieEnabled=YES' at the gdb
prompt, I get this response: $1 = <error type>
I found some code examples on Google about NSZombieEnabled that showed
setting the variable progamatically. The code compiled and ran in
debug, but I got no logging. I also tried it from the terminal, but my
apps menus wouldn't come up so I could do anything.

On Monday, December 16, 2002, at 12:06 PM, Mike Ferris wrote:

> This is the classic kind of backtrace that should make you think:
> "NSZombieEnabled".
>
> Start your app in the debugger, break on main. When you hit the
> breakpoint do:
>
> p NSZombieEnabled=YES
>
> Continue the app. Go to where it crashes and see what gets logged.
> You should find out what kind of freed object is in your pool and may
> get some advice on further breakpoints to set to narrow things down
> further.
>
> Zombie tracking is a really useful thing for tracking down
> over-released objects. And once you figure out what kind of object is
> being over-released, if the cause is not obvious, ObjectAlloc can be
> helpful in tracking it down further...
>
> Mike
>
>
> Begin forwarded message:
>
>> From: Matthew Smith <email@hidden>
>> Date: Sun Dec 15, 2002 8:46:11 PM US/Pacific
>> To: <email@hidden>, Cocoa Developer <email@hidden>
>> Subject: Re: Debug Help
>>
>>> I'm sure this is a memory management issue, but I'm going blind
>>> trying
>>> to find it.
>>
>> Sorry Tony, I can't help you, I've got the same issues, only mine is
>> shorter!!!
>>
>> #0 0x9068ba54 in objc_msgSend ()
>> #1 0x907e2660 in NSPopAutoreleasePool ()
>> #2 0x930ca374 in -[NSApplication run] ()
>> #3 0x000ddb8c in main (argc=1, argv=0xbffffc10) at
>> source/main.mm:15/Users/mps/Programming/ViewBuild
>> Source/ViewBuild/
>> #4 0x00002e28 in _start (argc=1, argv=0xbffffc10, envp=0xbffffc18) at
>> /SourceCache/Csu/Csu-45/crt.c:267/SourceCache/Csu/Csu-45/
>> #5 0x00002ca8 in start ()
>>
>> Is there a way to find out what object is causing this (it's type or
>> name???)
>>
>> I assume this is caused when an object is removed, but a call is made
>> to it.
>>
>> Cheers
>>
>> Matt
>> _______________________________________________
>> cocoa-dev mailing list | email@hidden
>> Help/Unsubscribe/Archives:
>> http://www.lists.apple.com/mailman/listinfo/cocoa-dev
>> Do not post admin requests to the list. They will be ignored.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.

References: 
 >Re: Debug Help (From: Mike Ferris <email@hidden>)

  • Prev by Date: Re: Debug Help
  • Next by Date: NSTextView headers and footers?
  • Previous by thread: Re: Debug Help
  • Next by thread: Re: Debug Help
  • Index(es):
    • Date
    • Thread