这是一个很好的帖子。以下是我的经验:我在属性声明中搞砸了retain/assign关键字。我说:

@property (nonatomic, assign) IBOutlet UISegmentedControl *choicesControl;
@property (nonatomic, assign) IBOutlet UISwitch *africaSwitch;
@property (nonatomic, assign) IBOutlet UISwitch *asiaSwitch;

我该说什么来着

@property (nonatomic, retain) IBOutlet UISegmentedControl *choicesControl;
@property (nonatomic, retain) IBOutlet UISwitch *africaSwitch;
@property (nonatomic, retain) IBOutlet UISwitch *asiaSwitch;

从你的描述中，我怀疑最有可能的解释是你在内存管理中出现了一些错误。你说你已经在iPhone开发上工作了几个星期，但没有说你是否对Objective C有一般的经验。如果你来自其他背景，在你真正内化内存管理规则之前可能需要一段时间——除非你把它说得很重要。

记住，你从分配函数(通常是静态的alloc方法，但也有一些其他方法)或复制方法获得的任何东西，你也拥有内存，当你完成时必须释放它。

But if you get something back from just about anything else including factory methods (e.g. [NSString stringWithFormat]) then you'll have an autorelease reference, which means it could be released at some time in the future by other code - so it is vital that if you need to keep it around beyond the immediate function that you retain it. If you don't, the memory may remain allocated while you are using it, or be released but coincidentally still valid, during your emulator testing, but is more likely to be released and show up as bad access errors when running on the device.

追踪这些东西的最好方法，也是一个好主意(即使没有明显的问题)是在Instruments工具中运行应用程序，特别是带有Leaks选项。

根据我的经验，这通常是由非法内存访问引起的。检查所有指针，特别是对象指针，以确保它们已初始化。确保你的主窗口。Xib文件(如果您正在使用的话)已正确设置，并具有所有必要的连接。

If none of that on-paper checking turns anything up, and it doesn't happen when single-stepping, try to locate the error with NSLog() statements: sprinkle your code with them, moving them around until you isolate the line that's causing the error. Then set a breakpoint on that line and run your program. When you hit the breakpoint, examine all the variables, and the objects in them, to see if anything doesn't look like you expect.I'd especially keep an eye out for variables whose object class is something you didn't expect. If a variable is supposed to contain a UIWindow but it has an NSNotification in it instead, the same underlying code error could be manifesting itself in a different way when the debugger isn't in operation.

我发现在objc_exception_throw上设置断点很有用。这样，当您获得EXC_BAD_ACCESS时，调试器应该会中断。

说明可以在这里找到调试技术

当你有无限递归的时候，我认为你也会有这个错误。这是我的案子。

忘记从dealloc中取出一个非alloc指针。我在我的UINavigationController的rootView上获得了exc_bad_access，但只是有时。我假设问题出在rootView上，因为它在viewDidAppear{}中崩溃了。它只发生在我用坏的dealloc{}发布弹出视图之后，这就是它!

"EXC_BAD_ACCESS"[切换到进程330]现在没有可用的内存来编程:调用malloc不安全

我认为这是一个问题，我试图分配…不是在我试图释放非alloc的地方，天哪!