• 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: GuardMalloc vs. auval
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GuardMalloc vs. auval


  • Subject: Re: GuardMalloc vs. auval
  • From: Daniel Jalkut <email@hidden>
  • Date: Mon, 15 May 2006 15:43:02 -0400

Doug, Bill: Thanks so much for responding.

Yes! Setting the MALLOC_ALTIVEC_SIZE env var eliminates the crashing behavior.

I'm sorry I didn't read the auval readme, but I'm glad that I posted here before reporting it as a bug.

Daniel

On May 15, 2006, at 3:32 PM, William Stewart wrote:

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:
40apple.com


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
References: 
 >GuardMalloc vs. auval (From: Daniel Jalkut <email@hidden>)
 >Re: GuardMalloc vs. auval (From: Daniel Jalkut <email@hidden>)
 >Re: GuardMalloc vs. auval (From: Doug Wyatt <email@hidden>)
 >Re: GuardMalloc vs. auval (From: William Stewart <email@hidden>)

  • Prev by Date: Re: GuardMalloc vs. auval
  • Next by Date: Compiling CoreAudio Examples
  • Previous by thread: Re: GuardMalloc vs. auval
  • Next by thread: 3DMixer and AudioFile crash
  • Index(es):
    • Date
    • Thread