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: Markus Hitter <email@hidden>
- Date: Thu, 29 Jun 2006 22:06:37 +0200
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.
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:
This email sent to email@hidden