> On Aug 25, 2016, at 3:02 PM, Jim Ingham <jing...@apple.com> wrote: > > Ah, maybe I was taking Carl's "apparently no reason" referencing lldb when he > meant no apparent reason in the debugee. I was concerned that he was seeing > the C++ exception breakpoint causing stops that didn't have an appropriate > stop reason in the lldb stop output or the in Xcode's pc ribbon. But > re-reading, it's quite likely that he really meant "I see no reason why this > code should be throwing exceptions".
No worries, I simply didn't understand why Xcode was breaking where it did. No program-related information was given in the call stack, so it took me a lot of time to track down what was causing it. The bug was difficult to reproduce because it happened only under certain tortured conditions (within a BTLE peripheral delegate callback method in which I would present a UIAlert on an intermittent write failure. Can't do that there; all is well now). Thanks for all the very interesting info! -Carl _______________________________________________ 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
