Re: How 'reliable' is MallocCheckHeap et al ?
Re: How 'reliable' is MallocCheckHeap et al ?
- Subject: Re: How 'reliable' is MallocCheckHeap et al ?
- From: Eric Albert <email@hidden>
- Date: Sun, 26 Sep 2004 17:08:25 -0700
On Sep 26, 2004, at 4:32 PM, Andrew Kimpton wrote:
Ultimately GuardMalloc did find this bug - where MallocDebug was
(sadly) no help at all.
Terrific! (That Guard Malloc worked, that is...not that MallocDebug
didn't.)
I have to repeat that GuardMalloc was much better here than either of
the other options. I wonder if the restrictions about altivec
instructions will be removed some time soon (would be nice - this app
uses them so if I have a problem deeper into the app I'm SOL using
GuardMalloc)
Take a look at the MALLOC_ALTIVEC_SIZE environment variable mentioned
in the libgmalloc man page -- set that and it should work. I've never
actually had to use this variable, though. I wonder if it's because
most AltiVec allocations are done in vector-sized units, which are
always going to be a multiple of 16 and therefore would be 16-byte
aligned by libgmalloc by default.
P.S. I miss those old Kon & Bal puzzle pages, at least (I think)
they're archived on the Mac Tech site.
Same here. They went away, but the kinds of problems they were solving
certainly didn't....
-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