(null) libc++abi.dylib:终止调用抛出异常 [英] (null) libc++abi.dylib: terminate called throwing an exception

查看:22
本文介绍了(null) libc++abi.dylib:终止调用抛出异常的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我使用 Xcode 4.5PR 和 iOS 6beta 2.

I use Xcode 4.5PR and iOS 6beta 2.

我没有更改任何代码,我的应用程序抛出了标题中提到的异常.

I didn't change any codes, my application throw an exception mentioned in the Title.

我使用了导致此异常的函数的调试窗口,但它显示

I used Debug Window which function caused this exception, but it showing

0x38dda960:  push   {r4, r5, r6, r7, lr}

我怎样才能找到问题?我该如何解决?

How can I find a problem? How can I fix it?

推荐答案

如果您没有进行任何更改,这可能只是与目前的 iOS 6 beta 相关.

If you didn't change anything, this could just simply be related to the iOS 6 beta as it currently stands.

1) 它可能是您选择为以下对象构建相同代码的模拟器:

如果您没有更改任何源代码,请检查以确保您的方案仍然指向它上次使用的同一个模拟器.(例如,尝试呈现一个模态视图控制器 (presentModalViewController:),但忘记有条件地为 iPad 使用弹出框,可能会导致这种情况.)

If you haven't changed any source code, check to make sure your scheme is still pointing to the same simulator that it last worked on. (For example, trying to present a modal view controller (presentModalViewController:), but forgetting to conditionally use a popover for iPad, could cause this.)

2) 如果堆栈跟踪和控制台没有帮助:

有时,堆栈中唯一的东西是 mainUIApplicationMain,这使得很难跟踪您自己的源代码中出了什么问题.这可能表明您正在调用或导致调用的本机框架方法出现问题.

Sometimes, the only things in the stack are main and UIApplicationMain, which makes it difficult to trace what went wrong in your own source. This is likely a sign that something is failing in a native framework method that you're calling or causing to be called.

如果控制台中未列出任何方法或特定对象,并且堆栈跟踪未指向您自己的类中的任何方法,请尝试将执行范围尽可能缩小到引发异常的点.在黑暗中选择断点时,我倾向于使用二分搜索方法,选择一个枢轴点并上下移动执行顺序,并根据需要选择一个新的中途"点.

If no method or specific object is listed in the console and the stack trace does not point to any methods from your own classes, try to narrow down the execution as close as you can to the point at which the exception is thrown. When picking breakpoints in the dark, I tend to use a binary search approach, picking a pivot point and moving up and down the execution order and picking a new "halfway" point as necessary.

这篇关于(null) libc++abi.dylib:终止调用抛出异常的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
相关文章
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆