Re: can I catch an EXC_BAD_ACCESS?
Re: can I catch an EXC_BAD_ACCESS?
- Subject: Re: can I catch an EXC_BAD_ACCESS?
- From: "Mark Wagner" <email@hidden>
- Date: Thu, 29 Jun 2006 15:21:51 -0700
On 6/29/06, Steve Checkoway <email@hidden> wrote:
On Jun 29, 2006, at 2:17 PM, David Alger wrote:
>
> On Jun 29, 2006, at 3:06 PM, Markus Hitter wrote:
>>
>> Am 25.06.2006 um 06:46 schrieb Peter CK:
>>> On 6/24/06, Matt Neuburg <email@hidden> wrote:
>>>>
>>>> Under certain conditions (out of my control) my app gets an
>>>> EXC_BAD_ACCESS.
>>
>> It's your app, so it's under your control.
>
> Suppose you have an app named Fob. Fob links to a third party
> library called FooLib. In FooLib contains a function, FooA, that
> you must use. Inside of FooA your app is receiving EXC_BAD_ACCESS
> exceptions periodically, because FooA is accessing non-allocated or
> already disposed memory. You don't have the source for FooLib, and
> the developer of it hasn't fixed FooA.
>
> Would the above scenario be classified as TOTALLY under the
> developer of Fobs control?
Despite being totally hypothetical, if you're passing an invalid
pointer, I'd say that it's totally under your control. If the library
itself is screwing up, then don't use the library, again under your
control.
And when the users of your application start flooding your help desk
with bug reports because a third-party plugin is buggy, what do you
do?
--
Mark Wagner
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden