Re: Just a quick verification on a bad access cause.

2016-02-09 Thread Alex Zavatone
On Feb 8, 2016, at 5:10 PM, Jens Alfke wrote: > >> On Feb 8, 2016, at 1:47 PM, Alex Zavatone wrote: >> >> if ( [myIVar respondsToSelector:@selector(someMethod)] { >> EXC_BAD_ACCESS (code=1, address=0x143545358) >> I did a po on myiVar and I get an address or 0x00014f05ee00 > > 0x143545358

Re: Just a quick verification on a bad access cause.

2016-02-08 Thread Jens Alfke
> On Feb 8, 2016, at 1:47 PM, Alex Zavatone wrote: > > if ( [myIVar respondsToSelector:@selector(someMethod)] { > EXC_BAD_ACCESS (code=1, address=0x143545358) > I did a po on myiVar and I get an address or 0x00014f05ee00 0x143545358 is probably the (bogus) class-info pointer it got from the

Just a quick verification on a bad access cause.

2016-02-08 Thread Alex Zavatone
iOS 9.x, Xcode 7.1. I'm sitting in the middle of the debugger, looking at some code I inherited and in a regular service, BLAM, EXC_BAD_ACCESS. This code uses ivars that are named the same as the properties :/ and what I noticed, we have this statement where the bad access is appearing: if ( [