• 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: How exactly are we supposed to debug memory problems???
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How exactly are we supposed to debug memory problems???


  • Subject: Re: How exactly are we supposed to debug memory problems???
  • From: Scott Ribe <email@hidden>
  • Date: Thu, 17 Aug 2006 06:57:49 -0600
  • Thread-topic: How exactly are we supposed to debug memory problems???

> You can try using Guard Malloc, which you can enable in Xcode using
> the 'Debug' menu.

I should have noted that Guard Malloc is not useable in this case. Too many
memory allocations. It's very frustrating that malloc has the ability to
note the problem, but no effective way to BREAK on that problem and find
where it is.


--
Scott Ribe
email@hidden
http://www.killerbytes.com/
(303) 722-0567 voice


 _______________________________________________
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

References: 
 >Re: How exactly are we supposed to debug memory problems??? (From: "Stefan van den Oord" <email@hidden>)

  • Prev by Date: Re: How exactly are we supposed to debug memory problems???
  • Next by Date: Re: Weird inline/struct offset problem
  • Previous by thread: Re: How exactly are we supposed to debug memory problems???
  • Next by thread: Re: How exactly are we supposed to debug memory problems???
  • Index(es):
    • Date
    • Thread