No call stack on Exception in xCode 4
I got an exception I can’t back trace. I would like to know where the exception is thrown. Is there an option for that in xCode 4.2? As you can see the call stack is not much of a help. The only thing I know is that Iam trying to access an item in a NSArray at a faulty index.
All ideas are welcomed.
- How to interpret a crashlog with no references to a specific class
- iOS5 What does “Discarding message for event 0 because of too many unprocessed messages” mean?
- debugging “failed to launch in time” with xcode
- How to delete breakpoints in XCode
- How to print Core Data debug values?
- Xcode's 'po' fails to identify the variable I wish to study. Wny?
Solutions Collect From Internet About “No call stack on Exception in xCode 4”
Set a breakpoint on
objc_exception_throw and that will stop the program on that message.
… Or just set the Exception Breakpoint in Xcode. Too used to doing this stuff directly in gdb.
- Automatically cell selected UITableView
- Initializing MIDIMetaEvent structure
- NSDictionary to UITableView
- Is it possible to create multiple SSL certificates for providers that send APNs to the same Application?
- Snapchat style multiple ViewController access
- Optional unwrapping SKPhysics error
- How do I do a shallow query on Firebase iOS?
- wsdl2swift get only nil as result, connection Result is OK
- Using Unity3D in one of the iOS App's views
- Code signing entitlement errors: Same error-different cause
- Muting AVCapture shutter sound on iPhone
- Facebook SDK – iOS – Fail to share URL (Error 102)
- iOS 11 navigationItem.titleView Width Not Set
- Swift 3.1: Crash when custom error is converted to NSError to access its domain property
- NSUserDefault change notification handling in watchppExtension