• 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
Debugging memory smashers with GC
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Debugging memory smashers with GC


  • Subject: Debugging memory smashers with GC
  • From: Rob Keniger <email@hidden>
  • Date: Tue, 23 Dec 2008 10:19:36 +1000

Hi,

My app is using garbage collection and I'm running into a memory smasher bug where the app will crash at seemingly random times, with an EXE_BAD_ACCESS.

Obviously there is some reference to an object that is being released when I don't want it to be but I'm having a lot of trouble tracking it down as it is quite intermittent, so every time I fire up Instruments the crash never seems to occur.

I've tried using the MallocStackLoggingNoCompact environment variable with malloc_history but my results have been inconclusive at best.

What is the best way to go about looking for this type of bug with Garbage Collection enabled?

--
Rob Keniger



_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: Debugging memory smashers with GC
      • From: Bill Bumgarner <email@hidden>
  • Prev by Date: Re: Replacing objects
  • Next by Date: Re: Debugging memory smashers with GC
  • Previous by thread: Re: Replacing objects
  • Next by thread: Re: Debugging memory smashers with GC
  • Index(es):
    • Date
    • Thread