1. Switch the Navigator view to the Breakpoint Navigator view, or you can use the shortcut key command+7 one step, the keyboard is the window style user Command key is the win key (with Microsoft logo), and then click on the lower left corner of the + sign, select Add Symbolic breakpoint This option
2. After the edit box appears, enter -[nsexception raise]in the Symbol tab, make sure you enter it correctly, and click the other area outside the edit box to OK (there is no done option in the Xcode6.4 version)
3. The steps to add Objc_exception_throw are consistent with the previous step, and if there is a spelling error, you can click the right button and select Edit Breakpoint to edit it again.
4. Here is where the compiler shows the error of code compilation after running (Command+r), where our global breakpoint section ends!
When one day you come across a situation where the editor area will always end up in a bunch of unintelligible stuff when debugging the code, instead of ending up in the error code as shown above, you can turn over the options in the menu again and again, and it will ultimately be useless, In this way, let the interface appear in your eyes again and again, the answer is naturally negative.
The solution is to uncheck the debug workflow>>always Show disassembly below the DEBUG option!
Xcode Global Breakpoint