• 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
Dealing with never-alocated bugs
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Dealing with never-alocated bugs


  • Subject: Dealing with never-alocated bugs
  • From: Thomas Davie <email@hidden>
  • Date: Sat, 11 Jun 2005 17:17:28 +0100

Hi,
I recently hit an interesting memory bug that took me about 12 hours of solid work to track down the source of. Zombies had done nothing useful and none of the memory profiling tools found the problem - I eventually had to resort to stripping bits out of the application until it stopped happening.


Anyway long-story-short, the reason that zombies produced nothing was that the object was never allocated, I was sending messages to nil. Is there any better way to approach problems like this that will catch the class of bug I'm talking about?

Bob

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: Dealing with never-alocated bugs
      • From: Ricky Sharp <email@hidden>
  • Prev by Date: Re: Cocoa menus in Carbon App
  • Next by Date: Re: Dealing with never-alocated bugs
  • Previous by thread: Re: Cocoa menus in Carbon App
  • Next by thread: Re: Dealing with never-alocated bugs
  • Index(es):
    • Date
    • Thread