[Lldb-commits] [lldb] r257513 - Fix TestThreadJump on Windows.

[Zachary Turner via lldb-commits]

Author: zturner
Date: Tue Jan 12 14:45:29 2016
New Revision: 257513

URL: http://llvm.org/viewvc/llvm-project?rev=257513&view=rev
Log:
Fix TestThreadJump on Windows.

The system can create threads for a system threadpool, so there is
no guarantee that the thread that is stopped is thread 1.  So use
a more robust check.

Modified:
    lldb/trunk/packages/Python/lldbsuite/test/functionalities/thread/jump/TestThreadJump.py

Modified: lldb/trunk/packages/Python/lldbsuite/test/functionalities/thread/jump/TestThreadJump.py
URL: http://llvm.org/viewvc/llvm-project/lldb/trunk/packages/Python/lldbsuite/test/functionalities/thread/jump/TestThreadJump.py?rev=257513&r1=257512&r2=257513&view=diff
==============================================================================
--- lldb/trunk/packages/Python/lldbsuite/test/functionalities/thread/jump/TestThreadJump.py (original)
+++ lldb/trunk/packages/Python/lldbsuite/test/functionalities/thread/jump/TestThreadJump.py Tue Jan 12 14:45:29 2016
@@ -34,8 +34,7 @@ class ThreadJumpTestCase(TestBase):
         # The stop reason of the thread should be breakpoint 1.
         self.expect("thread list", STOPPED_DUE_TO_BREAKPOINT + " 1",
             substrs = ['stopped',
-                       '* thread #1',
-                       'stop reason = breakpoint 1'])
+                       'main.cpp:{}, stop reason = breakpoint 1'.format(self.mark3)])
 
         self.do_min_test(self.mark3, self.mark1, "i", "4"); # Try the int path, force it to return 'a'
         self.do_min_test(self.mark3, self.mark2, "i", "5"); # Try the int path, force it to return 'b'