Why does assert simply terminate a program compiled for iPhone?

Question

I\'m debugging a heavily assert()\'ed iPhone app (Xcode, Objective-C++, and device simulator). In some cases, the assert failure would just terminate the app, instead of bre

Answer 1

In Xcode 4 and new iOS, NSAssert may actually take a variable list of parameters. This may be useful to log some values together with the assert. The compiling-out assert (see answer by Mike above) could be defined like this:

#ifdef DEBUG
#   define DAssert(A, B, ...) NSAssert(A, B, ##__VA_ARGS__);
#else
#   define DAssert(...);
#endif

Also, there is no longer Run → Show → Breakpoints menu item. See this post to set up Xcode 4 to break on an assert as defined above.