| |||
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
El 30/06/2008, a las 0:11, Chris Espinosa escribió:
Thanks to all for your replies. I actually have all sorts of problems related to the call stack with the debugger, for example the step over command usually does not work, and it performs a step into instead. This is annoying because it turns de debugger completely useless, without the ability to see the stack trace or to run the app step by step. I am using XCode 3.0 and yes, I compile the app as debug with compiler optimisation turned off and debug symbols generation enabled. I start to get frustrated about it because I don't get it. The exception that is thrown is a simple out of range access to an NSArray, which does not crash or hangs the app, so I am still more confused about it. I tend to think that the problem must be related to some misconfiguration of XCode or the debugger. By setting lots of breakpoints in my app I figured out that the origin of the problem is in the observeValueForKeyPath method of one of my controller objects, but again, breakpoints set in that method do not show any stack trace at all. Please help ! Joan Lluch. |
_______________________________________________ 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
| References: | |
| >objc_exception_throw (From: "Joan Lluch (casa)" <email@hidden>) | |
| >Re: objc_exception_throw (From: Jens Alfke <email@hidden>) | |
| >Re: objc_exception_throw (From: Chris Espinosa <email@hidden>) |
| Home | Archives | FAQ | Terms/Conditions | Contact | RSS | Lists | About |
Visit the Apple Store online or at retail locations.
1-800-MY-APPLE
Contact Apple | Terms of Use | Privacy Policy
Copyright © 2007 Apple Inc. All rights reserved.