Re: odd soundfile buffer problem
Re: odd soundfile buffer problem
- Subject: Re: odd soundfile buffer problem
- From: Brad Garton <email@hidden>
- Date: Sat, 22 May 2010 22:07:57 -0400
I found the problem, yay!
Like a big dummy, I assumed that since the crashes were occurring on the device, I should try to use Guard Malloc with XCode set to build on the device. Duh. Anyhow, once I got it set in debug mode, I traced it down to an obscure reference to a string pointer in my code that was indeed NULL. Oh these digital machines...
Anyhow, thanks for all the assistance!
brad
On May 22, 2010, at 5:54 AM, tahome izwah wrote:
> You can only set that option when you're not running a debug session.
> Also you will get a message stating that GuardMalloc is enabled when
> you debug your application. Keep in mind that it will execute a lot
> slower than normally so if this is caused by a race condition of some
> kind you will probably not get the same behaviour with GuardMalloc on.
>
> The problem you're describing sounds like it has something to do with
> not getting idle time and/or messed up run loops. Try adding a
> sleep(0) (or 1) instead of your printf statement just for grins to see
> if the problem goes away as well... if it does then you're probably
> stuck in a loop that doesn't leave your other tasks any room to
> breathe.
>
> --th
>
> 2010/5/22 Brad Garton <email@hidden>:
>> Thanks Eric --
>>
>> I'm suspecting something like this, or perhaps some variable scoping issues of some kind. But I can't figure it out! I tried enabling Gaurd Malloc (although I'm not sure I'm doing it -- the menu item never shows a happy little check when I select it), but no problems. That's what is so odd -- I have it to the point now where it works fine in debug mode, but when I compile in release mode I get no sound. No errors, no crashes, but no sound. I've tried moving the pointer declaration for the buffer I'm reading into outside object scope (grasping at straws here...), and the memory gets malloc'd fine, but still this weird disparity.
>>
>> I guess I'll keep on hacking away,
>>
>> brad
>>
>>
>> On May 21, 2010, at 12:15 PM, Eric Allamanche wrote:
>>
>>> when adding printf like statements make things work magically, then this hints at some heap/stack corruption issues. Have you checked that your buffers are large enough? Try enabling Guard Malloc and see what happens
>>
>> _______________________________________________
>> 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
>>
> _______________________________________________
> 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
>
_______________________________________________
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