Thanks for digging in and tracking that down Bill! Very much appreciated!
It actually makes sense with what I'm now reading about Collection Views.
And thanks Kyle. I've seen that breakpoint behavior before and just dealt
with it ... but your statement about hardware exceptions really clarifies
it
That's crashing because after going back, FirstViewController is using
SecondViewController as it's collectionView's delegate & dataSource, resulting
in messages to a dealloc-ed object. Turn on NSZombies to see this.
This appears to happen because when going Back from your
SecondViewController'
On Wed, May 20, 2015, at 01:12 PM, Alex Zavatone wrote:
> Whaaa?
>
> The app throws an exception, but setting an exception breakpoint never
> gets triggered?
EXC_BAD_ACCESS is a hardware exception. It has nothing to do with a
software exception (the kind thrown by @throw or +[NSException raise],
Whaaa?
The app throws an exception, but setting an exception breakpoint never gets
triggered?
Anyway, you may find these helpful.
http://loufranco.com/blog/understanding-exc_bad_access
http://www.touch-code-magazine.com/how-to-debug-exc_bad_access/
Enabling NSZombies may help you track that d
Thanks Alex,
I have set an exception breakpoint but it never fires - and I will
experiment with popping the second view controller programmatically and
scrolling up.
I think this has to do with my elementary understanding of how
UICollectionViews are reused in this type of transition animation -
What if you issue the back programatically and then scroll up?
It would be interesting to see just what gets unwired here.
Have you set an exception breakpoint to tell you exactly what is breaking?
On May 20, 2015, at 12:46 AM, Luther Baker wrote:
> I've got a simple iOS project consisting of 2
