• 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: Doug Wyatt <email@hidden>
  • Date: Mon, 15 May 2006 11:24:19 -0700

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


  • Follow-Ups:
    • Re: GuardMalloc vs. auval
      • From: William Stewart <email@hidden>
References: 
 >GuardMalloc vs. auval (From: Daniel Jalkut <email@hidden>)
 >Re: GuardMalloc vs. auval (From: Daniel Jalkut <email@hidden>)

  • Prev by Date: Sound Data question
  • Next by Date: Re: AMS is 'stuck' around device connect/disconnect
  • Previous by thread: Re: GuardMalloc vs. auval
  • Next by thread: Re: GuardMalloc vs. auval
  • Index(es):
    • Date
    • Thread