On Aug 25, 2016, at 12:55 , Jim Ingham <jing...@apple.com> wrote: > >> On Aug 25, 2016, at 12:31 PM, Alex Zavatone <z...@mac.com >> <mailto:z...@mac.com>> wrote: >> >>> This occurred while running my iOS app from Xcode, connected to my iPhone. >>> In Xcode I have the "All Exceptions" breakpoint disabled (otherwise it >>> would break in some thread for "apparently no reason"). Xcode generates >>> this backtrace in the bottom console log output area. >> >> OK, that's freaking strange. >> >> > > I agree with Alex. If you can reproduce this in something you can put in a > bug report, please file a bug and I'll take a whack at fixing it.
This is almost certain the known “issue” with frameworks that use exceptions for flow control instead of as crashes. This happens in several Apple-provided frameworks that are written in C++, because in C++ using exceptions for flow control is a normal pattern**. It *occasionally* happens in 3rd party frameworks written in Obj-C that don’t follow the rules for handling exceptions as crashes. You can mitigate the first case by turning off only C++ exceptions. If you run into the second case, there’s no really good solution. ** That said, it may be that Apple has tried to eliminate these cases in the last couple of years, so it may be worth bug-reporting anyway. If nothing else, it shines some light on the problem.
_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (Xcode-users@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to arch...@mail-archive.com
