IOS memory error debugging (EXC_BAD_ACCESS), iosexc_bad_access

Source: Internet
Author: User
Tags gdb debugger

IOS memory error debugging (EXC_BAD_ACCESS), iosexc_bad_access

Memory Error crash:

Thread Stack:

It may be caused by access to the released object. According to the field, no memory error is found for the specific object.

1. Enable zombie object debugging

Edit Scheme-> Debug-> Diagnostics-> Enable Zombie Objects

2. Check the console and check whether the output is a Button error.

16:40:49. 959 funmiosbr_ZQB [2761: 388881] ****-[UIButton setHidden:]: message sent to deallocated instance 0x185942a0

3. Because the default debugger of the new version of xcode is lldb, the earlier version of the gdb debugger can be viewed using the following command:

(Gdb) info malloc-history 0x185942a0

(1) Profile your project

(2) Select Zombies from the list of instruments

(3) Make your app trigger the problem

(4) At this point you shoshould be presented with the address that was already deallocated and you can adjust e it.

(5) locate the problem

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.