From 22eeb7227c9fcd4d6b5f6cddaacadece580002f4 Mon Sep 17 00:00:00 2001 From: Jim Ingham Date: Wed, 3 Feb 2016 19:45:31 +0000 Subject: The SetStopInfo from a Mach Exception was setting the stop reason to None when we stop due to a trace, then noticed that we were on a breakpoint that was not valid for the current thread. That should actually have set it back to trace. This was pr26441 () llvm-svn: 259684 --- .../breakpoint/consecutive_breakpoints/TestConsecutiveBreakpoints.py | 1 - 1 file changed, 1 deletion(-) (limited to 'lldb/packages/Python/lldbsuite/test/functionalities') diff --git a/lldb/packages/Python/lldbsuite/test/functionalities/breakpoint/consecutive_breakpoints/TestConsecutiveBreakpoints.py b/lldb/packages/Python/lldbsuite/test/functionalities/breakpoint/consecutive_breakpoints/TestConsecutiveBreakpoints.py index 8aa1ee75ef0..d2bd9f2812d 100644 --- a/lldb/packages/Python/lldbsuite/test/functionalities/breakpoint/consecutive_breakpoints/TestConsecutiveBreakpoints.py +++ b/lldb/packages/Python/lldbsuite/test/functionalities/breakpoint/consecutive_breakpoints/TestConsecutiveBreakpoints.py @@ -79,7 +79,6 @@ class ConsecutiveBreakpointsTestCase(TestBase): self.finish_test() @no_debug_info_test - @expectedFailureDarwin(bugnumber="llvm.org/pr26441") def test_single_step_thread_specific(self): """Test that single step stops, even though the second breakpoint is not valid.""" self.prepare_test() -- cgit v1.2.3