Daniel
Daniel

Reputation: 285

Debugging EXC_BAD_ACCESS

enter image description hereI've not worked on this project in quite some time.. When I left it some time in the iOS 8s it ran just fine, however.. on the latest XCode I'm getting many inconsistent EXC_BAD_ACCESS crashes. Now afaik it's requiring a deallocated object. However, the error is lacking where to look. This is quite a big project and like I say, the errors are inconsistent.

I've tried enabling zombie objects, as well as passing it as a starting parameter. However, this is leading me to no joy. I'm expecting something in the debug console with zombies enabled, is this right?

If anyone has any tips on how to find an easier way to debug this, as opposed to tinkering with everything and hoping it works..

Upvotes: 2

Views: 7099

Answers (2)

bbum
bbum

Reputation: 162712

EXC_BAD_ACCESS just means that your app is trying to access an invalid memory address. While it is oft caused be a deallocated object, that isn't always the case.

When the app crashes, there should be a crash log or backtrace. Post it as that'll provide clues.


Lovely; a crash entirely in framework code. Seeing as how it is SceneKit that is crashing, I would suggest replacing any graphic assets with new ones and see if that fixes it (even if it doesn't look right). Then check to make sure all of your geometries and layouts are correct.

Upvotes: 4

Anthony Castelli
Anthony Castelli

Reputation: 567

Have you tried adding a global Exception or Symbolic breakpoint? Those usually help me 99% of the time when I encounter issues without any sort of backtrace.

Upvotes: 0

Related Questions