Filtering by exception class only works for Swift at present. That’s a known issue. I don’t think we have a bug on the fact that the Xcode UI doesn’t reflect the current state of affairs.
Jim > On Aug 8, 2016, at 11:04 AM, Jens Alfke <j...@mooseyard.com> wrote: > > I want the debugger to stop when a specific type of C++ exception is thrown, > not on all exceptions. (I’m using the CppUnit test framework, and I want to > stop on assertion failures, not on internal exceptions thrown by my code.) > > So I: > 1. Click + in the Breakpoints navigator > 2. Click “Exception Breakpoint” > 3. Change “Type” to “C++” > 4. Fill in “CppUnit::Exception” in the Name field > > It doesn’t work — the debugger doesn’t stop at the exception. > (Regular “All C++ Exceptions” breakpoints, which I’ve been using, work fine.) > > On the other hand, if I set a Symbolic breakpoint at > “CppUnit::Exception::Exception”, it _does_ stop when an Exception object is > constructed (which is actually just as good from my perspective.) > > Should I file a bug report, or am I missing some subtlety of exception > breakpoints? > > —Jens > > PS: Xcode 8 beta 4, with a Mac OS target > _______________________________________________ > 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/jingham%40apple.com > > This email sent to jing...@apple.com _______________________________________________ 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
