Yes, I'm aware. That's everything Xcode shows; that's the full stack. I had hoped breaking on that message would break at the point of the send, not at the point of handling the unrecognized selector.
Sent from my iPhone On Jul 9, 2013, at 18:46, Jens Alfke <j...@mooseyard.com> wrote: > > On Jul 9, 2013, at 6:39 PM, Rick Mann <rm...@latencyzero.com> wrote: > >> It only happens in release builds, and the call stack shown in Xcode while >> debugging shows no source. I can't figure out where the call is: >> >> #0 0x39f9f960 in objc_exception_throw () >> #1 0x320fee06 in -[NSObject(NSObject) doesNotRecognizeSelector:] () > > What’s frame #2? That’s the code that’s sending -removeObject:. The frames > you listed are just the ones raising the exception. > >> I tried putting a symbolic breakpoint on -[__NSArrayI removeObject:], but it >> doesn't stop any earlier. I don't actually call remove-anything in my code >> anywhere. > > Well, there’s no such method — that’s exactly what that exception means — so > it’s not surprising that you can’t set a breakpoint on it :) > > —Jens _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
