Solutions for sigbat or exc_bad_access with botnets
With the development in xcode, I believe many developers are correct about sigbat or exc_bad_access. Some operations are performed during the runtime ~~ Jump to the main function, and then the previous prompt appears, very depressed, with little information. How to find it when there are too many programs, right.
Of course, apple, as a big company, is still well-considered. Here we will provide you with a method that will output the cause of sigbat or exc_bad_access on the console, basically 90% can solve your problem. Of course, you must understand some English. Okay. You don't have to talk about it.
Step 1,
Select Edit scheme. This box is displayed.
Select info by default, and then select arguments,
Add nszombieenabled to environment varibles. The final result is
Then select OK.
You don't believe it? You can build a project, add a button or something to the view, and release it before adding it. Compile and run it to see what is output on the console.
Haha, the first post. Hope to help you again!
Original article:
Http://www.devdiv.com/iOS_iPhone-%E5%85%B3%E4%BA%8E%E5%87%BA%E7%8E%B0%E5%83%B5%E5%B0%B8%E4%BF%A1%E5%8F%B7SIGBAT%E6%88%96%E8%80%85EXC_BAD_ACCESS%E7%9A%84%E8%A7%A3%E5%86%B3%E6%96%B9%E6%A1%88-thread-118126-1-1.html
I made a demo myself.
1: The following error message is reported without the nszombieenabled parameter (the prompt is hard to understand). The xcode error is located in Main. M.
Storyboarddemo [799: 207]-[_ nscfstring frame]: Unrecognized selector sent to instance 0x6b22250
2: After this parameter is added, the following error message is reported. The xcode error location is accurately located on the wrong code line.
-[Uibutton superview]: Message sent to deallocated instance 0x6a26d60