• 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: can I catch an EXC_BAD_ACCESS?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: can I catch an EXC_BAD_ACCESS?


  • Subject: Re: can I catch an EXC_BAD_ACCESS?
  • From: David Alger <email@hidden>
  • Date: Thu, 29 Jun 2006 16:17:32 -0500


On Jun 29, 2006, at 3:06 PM, Markus Hitter wrote:


Am 25.06.2006 um 06:46 schrieb Peter CK:

EXC_BAD_ACCESS means
that I have to kill x-code and restart my machine. Everything freezes up and
the same thing happens again unless I restart.

You have a userland application causing the whole OS to freeze? That'd be a great contribution to <rdar://4578834>. Wait - how do you "kill Xcode" when everything is frozen?



Matt, what type of bug did you find in your code that was causing
EXC_BAD_ACCESS ?

EXC_BAD_ACCESS is a very general error (memory space violation), there are millions of possible reasons.



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?

David

Also: In Xcode, when this happens, I fall into the debugger window. I would
prefer instead to have the app crash so that I can see what the end user
would see. How can I arrange for that?

There's a preference for wether you fall into the debugger, but you really, really want to fix this regardless of this preference's setting.



Markus

- - - - - - - - - - - - - - - - - - -
Dipl. Ing. Markus Hitter
http://www.jump-ing.de/




_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40millertel.net


This email sent to email@hidden


_______________________________________________ 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
  • Follow-Ups:
    • Re: can I catch an EXC_BAD_ACCESS?
      • From: Steve Checkoway <email@hidden>
References: 
 >can I catch an EXC_BAD_ACCESS? (From: Matt Neuburg <email@hidden>)
 >Re: can I catch an EXC_BAD_ACCESS? (From: "Peter CK" <email@hidden>)
 >Re: can I catch an EXC_BAD_ACCESS? (From: Markus Hitter <email@hidden>)

  • Prev by Date: Re: can I catch an EXC_BAD_ACCESS?
  • Next by Date: Re: XCode ld and static lib.a files...
  • Previous by thread: Re: can I catch an EXC_BAD_ACCESS?
  • Next by thread: Re: can I catch an EXC_BAD_ACCESS?
  • Index(es):
    • Date
    • Thread