Currently, my Xcode4 does not stop at NSAssert
failure. How can I make it stop at NSAssert
failure again?
相关问题
- Apple PrefPane example fails to build with clang e
- XCode 4.2 clang seg fault
- How do I change the compiler in Xcode
- How do I add OpenGL Mathematics (GLM) to Xcode 4?
- How do you link a C++ static library to a C progra
相关文章
- Generate code for core data attributes in xcode 4
- UITableViewController Background Image
- Can't Rename Files In Xcode 4 Anymore?
- How do I navigate through a method call hierarchy
- can't find info.plist in xcode 4
- What should I do about xcuserdata directories with
- reloadData in MasterView from DetailView
- How to debug “Xcode CodeSign error: The entitlemen
Now you will stop in the debugger as soon as NSAssert fires. In my testing, it goes to the nearest source code and doesn't just show you the assembly where you set the breakpoint.
More Generically, you could do this:
This may be more or less useful depending on your code.
See also the XCode 4 documentation result for "Adding an Exception Breakpoint"
i'm boring for the problem. i think blow blog may be useful. http://www.learn-cocos2d.com/tag/nsassert/ http://edmundlong.com/edsBlog/making-nsassert-work/
Assertions are automatically disabled, by default, in a Release build. If you want assertions to work, do a Debug build, or turn off the Other C Flags build setting where assertions are turned off in the Release build.