Re: ExtAudioFileRead Crash
Re: ExtAudioFileRead Crash
- Subject: Re: ExtAudioFileRead Crash
- From: William Stewart <email@hidden>
- Date: Mon, 12 Oct 2009 12:19:54 -0700
On Oct 12, 2009, at 12:08 PM, tahome izwah wrote:
2009/10/12 William Stewart <email@hidden>:
This is a new call in SnowLeopard. We added this in a couple of
places
because, well clients are passing us bogus buffers and we write
over memory
we shouldn't.
But if you detect that there is something strange going on
couldn't/shouldn't you do some sanity checks and degrade gracefully
rather than crash?
you can only "detect" this by trying to do the read and causing the
crash.
The point of this call is to provide a known point of failure, rather
than some random corruption at some point in the future..
I'm sure you have your reasons for this but I am simply curious as to
what they are...
Thanks
--th
_______________________________________________
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