Lists

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: "Stefan van den Oord" <email@hidden>
Date: Thu, 17 Aug 2006 14:39:10 +0200

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

Stefan

On 8/17/06, Scott Ribe <email@hidden> wrote:

I've got a double free. MallocBadFreeAbort doesn't abort. Setting a break in
szone_error doesn't do anything either. Setting a break in malloc_printf
does work, but that's mostly useless to me because I also need to use
MallocCheckHeapStart & Each.

XCode 2.4, OS X 10.4.7.

--
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

_______________________________________________
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 exactly are we supposed to debug memory problems???
From: Scott Ribe <email@hidden>


References:  
  >How exactly are we supposed to debug memory problems??? (From: Scott Ribe <email@hidden>)




Prev by Date:
Re: Weird inline/struct offset problem

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

Previous by thread:
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