Fwd: can I catch an EXC_BAD_ACCESS?
Fwd: can I catch an EXC_BAD_ACCESS?
- Subject: Fwd: can I catch an EXC_BAD_ACCESS?
- From: "Peter CK" <email@hidden>
- Date: Thu, 29 Jun 2006 16:58:08 -0400
---------- Forwarded message ----------
From: Peter CK <email@hidden>
Date: Jun 29, 2006 4:57 PM
Subject: Re: can I catch an EXC_BAD_ACCESS?
To: j o a r <email@hidden>
> Hmmm.... if only xcode would be so kind to provide me with a call
> stack.
A backtrace of what? If you're in the debugger and get an exception
or crash, you can get a backtrace easily if you want to. If you crash
while not in the debugger, Xcode will attach the debugger for you. I
don't see what else you could be looking for?
I'm assuming by backtrace, you mean a call stack. I don't get one when I get the EXC_BAD_ACCESS. I'm working with a dev build that I ran from within X-code.
It works fine with any other type of error or crash... I get a call stack and I can figure out what I did wrong.
In this case, nothin... My app freezes, no call stack. Unless I restart my machine, the exact same thing happens again. So in short, I'm looking for a call stack within the debug environment.
_______________________________________________
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