• 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 'reliable' is MallocCheckHeap et al ?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How 'reliable' is MallocCheckHeap et al ?


  • Subject: Re: How 'reliable' is MallocCheckHeap et al ?
  • From: Eric Albert <email@hidden>
  • Date: Fri, 24 Sep 2004 19:28:36 -0700

On Sep 24, 2004, at 11:07 AM, Andrew Kimpton wrote:

I'm struggling to chase down what at first glance should be a relatively simple memory smashing bug.

I'm using the MallocDebug environment variables :

Have you tried using Guard Malloc? It catches memory smashers very effectively and pinpoints the exact place of the fault. (It also causes your application to run about 100x slower than normal, but that's worth it when you catch a memory smasher as a result.)


See the libgmalloc man page for instructions and other details.

Hope this helps,
Eric

_______________________________________________
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


  • Follow-Ups:
    • Re: How 'reliable' is MallocCheckHeap et al ?
      • From: Andrew Kimpton <email@hidden>
References: 
 >How 'reliable' is MallocCheckHeap et al ? (From: Andrew Kimpton <email@hidden>)

  • Prev by Date: mode1 troubles
  • Next by Date: Re: FAQ: How do you debug a C++ Standard Tool Application?
  • Previous by thread: How 'reliable' is MallocCheckHeap et al ?
  • Next by thread: Re: How 'reliable' is MallocCheckHeap et al ?
  • Index(es):
    • Date
    • Thread