Although in my case, 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. No call stack, no nothin,
just craps on me. It might be because I'm using xcode 2.2, but I am
quite certain that X-code does not handle this type of error very
gracefully.
This is certainly a problem with your machine, and not with Xcode,
because that's not how it works for everyone else. Try to uninstall
and reinstall Xcode. Failing that, try something more drastic, like
reinstalling your entire machine.
On 29 jun 2006, at 15.55, Peter CK wrote:
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?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xcode-users/email@hidden
This email sent to email@hidden
