Home/ Questions/Exc_bad_access code 1 - simple way to solve it
Next
Answered
Harper Miller
  • 22
Asked: 2022-05-18T16:47:37+00:00 In:

Exc_bad_access code 1 – simple way to solve it

  • 22

. Advertisement .

..3..

. Advertisement .

..4..

I am new to programs and searching the “exc_bad_access code 1” to understand it better. It seems it doesn’t work as expected when I used some suggestions before. Here is the command line I use:

int retVal;
  @try {
  retVal = UIApplicationMain(argc, argv, nil, NSStringFromClass([AppDelegate class]));
  */\ error is here**
  }
  @catch (NSException *exception) {
  NSLog(@"%@", [exception callStackSymbols]);
  @throw exception;
  }
  return retVal;

The error I’m getting is below:

Thread 1: EXC_BAD_ACCESS (code=1, address=0xf00000c)

Please give me the solution to this issue.

exc_bad_access
Share

2 Answers

  1. Best Answer
    Expert

    The cause:

    This issue is probably hidden deep within your code, as stated in a comment. A zombie is the culprit that causes this error.

    Solution:

    The simplest way to solve this error is using culprit itself, zombie, (ideally on the most recent version of Xcode, which is Xcode 5 due to improvements) under profiler and select “Zombies”. You can view the history of everything that has ever happened to the item if it fails.

    You can also set a breakpoint for an exception as well. Instead of in main, where the exception is passed up, you may obtain a break when the issue occurs.

    • 0

  2. This problem was solved with Zombies. The problem was solved with [UIScrollView(UIScrollViewInternal) _notifyDidScroll]

    I added 

    - (void)dealloc {

 self.tableView.delegate = nil;

}

    This issue was limited to iOS 7.

    Thanks for help!

    • 16

Leave an answer

You must login to add an answer.

Need An Account,