Re: GuardMalloc vs. auval
Re: GuardMalloc vs. auval
- Subject: Re: GuardMalloc vs. auval
- From: William Stewart <email@hidden>
- Date: Mon, 15 May 2006 12:32:00 -0700
These are described as required steps in the auval read me:
Testing for Memory Smashers
(1) You need to define the following three environment variables
DYLD_FORCE_FLAT_NAMESPACE=1
DYLD_INSERT_LIBRARIES=/usr/lib/libgmalloc.dylib
MALLOC_ALTIVEC_SIZE=1
(2) Execute auval - you'll see something like the following:
[~] % auval -v aufx bpas appl -q
Allocations will be placed on 16 byte boundaries.
- Some buffer overruns may not be noticed.
- Applications using AltiVec instructions will work.
GuardMalloc-4
There aren't any known problems with auval and any of the memory
debugging tools that are described in this read me. I also think that
AULab is ok in this area too.
On 15/05/2006, at 11:24 AM, Doug Wyatt wrote:
Do the problems disappear if you set the environment variable
MALLOC_ALTIVEC_SIZE ?
Doug
On May 14, 2006, at 09:38 , Daniel Jalkut wrote:
Update: I am also unable to run against Guard Malloc with AULab. I
am however able to run my Audio Unit against Guard Malloc in
GarageBand.
So I'm assuming that both auval and AULab have some issues that
need correcting so that they themselves can run safely against
Guard Malloc.
Daniel
--
Doug Wyatt
Core Audio, Apple
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
--
mailto:email@hidden
tel: +1 408 974 4056
________________________________________________________________________
__
"Much human ingenuity has gone into finding the ultimate Before.
The current state of knowledge can be summarized thus:
In the beginning, there was nothing, which exploded" - Terry Pratchett
________________________________________________________________________
__
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden