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: "Peter CK" <email@hidden>
- Date: Thu, 29 Jun 2006 17:14:34 -0400
On 6/29/06, Markus Hitter <email@hidden> 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?
Well, maybe frozen isn't the correct term. My app is frozen, but I can exit X-code normally. I'm just saying that unless I restart, the same thing happens again.
There is no call stack. It says something about an inner frame and a corupt stack underneath the EXC_BAD_ACCESS error message. I'll write it down the next time I see it.
>> 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.
Which preference are you refering to?
Peter
_______________________________________________
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