Currently most of the test files have a separate dwarf and a separate dsym test with almost identical content (only the build step is different). With adding dwo symbol file handling to the test suit it would increase this to a 3-way duplication. The purpose of this change is to eliminate this redundancy with generating 2 test case (one dwarf and one dsym) for each test function specified (dwo handling will be added at a later commit). Main design goals: * There should be no boilerplate code in each test file to support the multiple debug info in most of the tests (custom scenarios are acceptable in special cases) so adding a new test case is easier and we can't miss one of the debug info type. * In case of a test failure, the debug symbols used during the test run have to be cleanly visible from the output of dotest.py to make debugging easier both from build bot logs and from local test runs * Each test case should have a unique, fully qualified name so we can run exactly 1 test with "-f <test-case>.<test-function>" syntax * Test output should be grouped based on test files the same way as it happens now (displaying dwarf/dsym results separately isn't preferable) Proposed solution (main logic in lldbtest.py, rest of them are test cases fixed up for the new style): * Have only 1 test fuction in the test files what will run for all debug info separately and this test function should call just "self.build(...)" to build an inferior with the right debug info * When a class is created by python (the class object, not the class instance), we will generate a new test method for each debug info format in the test class with the name "<test-function>_<debug-info>" and remove the original test method. This way unittest2 see multiple test methods (1 for each debug info, pretty much as of now) and will handle the test selection and the failure reporting correctly (the debug info will be visible from the end of the test name) * Add new annotation @no_debug_info_test to disable the generation of multiple tests for each debug info format when the test don't have an inferior Differential revision: http://reviews.llvm.org/D13028 llvm-svn: 248883
142 lines
6.0 KiB
Python
142 lines
6.0 KiB
Python
"""
|
|
Test that lldb watchpoint works for multiple threads.
|
|
"""
|
|
|
|
import os, time
|
|
import unittest2
|
|
import re
|
|
import lldb
|
|
from lldbtest import *
|
|
import lldbutil
|
|
|
|
class WatchpointForMultipleThreadsTestCase(TestBase):
|
|
|
|
mydir = TestBase.compute_mydir(__file__)
|
|
|
|
@expectedFailureAndroid(archs=['arm', 'aarch64']) # Watchpoints not supported
|
|
@expectedFailureWindows("llvm.org/pr24446") # WINDOWS XFAIL TRIAGE - Watchpoints not supported on Windows
|
|
def test_watchpoint_multiple_threads(self):
|
|
"""Test that lldb watchpoint works for multiple threads."""
|
|
self.build()
|
|
self.setTearDownCleanup()
|
|
self.hello_multiple_threads()
|
|
|
|
@expectedFailureAndroid(archs=['arm', 'aarch64']) # Watchpoints not supported
|
|
@expectedFailureWindows("llvm.org/pr24446") # WINDOWS XFAIL TRIAGE - Watchpoints not supported on Windows
|
|
def test_watchpoint_multiple_threads_wp_set_and_then_delete(self):
|
|
"""Test that lldb watchpoint works for multiple threads, and after the watchpoint is deleted, the watchpoint event should no longer fires."""
|
|
self.build()
|
|
self.setTearDownCleanup()
|
|
self.hello_multiple_threads_wp_set_and_then_delete()
|
|
|
|
def setUp(self):
|
|
# Call super's setUp().
|
|
TestBase.setUp(self)
|
|
# Our simple source filename.
|
|
self.source = 'main.cpp'
|
|
# Find the line number to break inside main().
|
|
self.first_stop = line_number(self.source, '// Set break point at this line')
|
|
|
|
def hello_multiple_threads(self):
|
|
"""Test that lldb watchpoint works for multiple threads."""
|
|
self.runCmd("file %s" % os.path.join(os.getcwd(), 'a.out'), CURRENT_EXECUTABLE_SET)
|
|
|
|
# Add a breakpoint to set a watchpoint when stopped on the breakpoint.
|
|
lldbutil.run_break_set_by_file_and_line (self, None, self.first_stop, num_expected_locations=1)
|
|
|
|
# Run the program.
|
|
self.runCmd("run", RUN_SUCCEEDED)
|
|
|
|
# We should be stopped again due to the breakpoint.
|
|
# The stop reason of the thread should be breakpoint.
|
|
self.expect("thread list", STOPPED_DUE_TO_BREAKPOINT,
|
|
substrs = ['stopped',
|
|
'stop reason = breakpoint'])
|
|
|
|
# Now let's set a write-type watchpoint for variable 'g_val'.
|
|
# The main.cpp, by design, misbehaves by not following the agreed upon
|
|
# protocol of using a mutex while accessing the global pool and by not
|
|
# writing to the variable.
|
|
self.expect("watchpoint set variable -w write g_val", WATCHPOINT_CREATED,
|
|
substrs = ['Watchpoint created', 'size = 4', 'type = w'])
|
|
|
|
# Use the '-v' option to do verbose listing of the watchpoint.
|
|
# The hit count should be 0 initially.
|
|
self.expect("watchpoint list -v",
|
|
substrs = ['hit_count = 0'])
|
|
|
|
while True:
|
|
self.runCmd("process continue")
|
|
|
|
self.runCmd("thread list")
|
|
if "stop reason = watchpoint" in self.res.GetOutput():
|
|
# Good, we verified that the watchpoint works!
|
|
self.runCmd("thread backtrace all")
|
|
break
|
|
else:
|
|
self.fail("The stop reason should be either break or watchpoint")
|
|
|
|
# Use the '-v' option to do verbose listing of the watchpoint.
|
|
# The hit count should now be 1.
|
|
self.expect("watchpoint list -v",
|
|
substrs = ['hit_count = 1'])
|
|
|
|
def hello_multiple_threads_wp_set_and_then_delete(self):
|
|
"""Test that lldb watchpoint works for multiple threads, and after the watchpoint is deleted, the watchpoint event should no longer fires."""
|
|
self.runCmd("file %s" % os.path.join(os.getcwd(), 'a.out'), CURRENT_EXECUTABLE_SET)
|
|
|
|
# Add a breakpoint to set a watchpoint when stopped on the breakpoint.
|
|
lldbutil.run_break_set_by_file_and_line (self, None, self.first_stop, num_expected_locations=1)
|
|
|
|
# Run the program.
|
|
self.runCmd("run", RUN_SUCCEEDED)
|
|
|
|
# We should be stopped again due to the breakpoint.
|
|
# The stop reason of the thread should be breakpoint.
|
|
self.expect("thread list", STOPPED_DUE_TO_BREAKPOINT,
|
|
substrs = ['stopped',
|
|
'stop reason = breakpoint'])
|
|
|
|
# Now let's set a write-type watchpoint for variable 'g_val'.
|
|
# The main.cpp, by design, misbehaves by not following the agreed upon
|
|
# protocol of using a mutex while accessing the global pool and by not
|
|
# writing to the variable.
|
|
self.expect("watchpoint set variable -w write g_val", WATCHPOINT_CREATED,
|
|
substrs = ['Watchpoint created', 'size = 4', 'type = w'])
|
|
|
|
# Use the '-v' option to do verbose listing of the watchpoint.
|
|
# The hit count should be 0 initially.
|
|
self.expect("watchpoint list -v",
|
|
substrs = ['hit_count = 0'])
|
|
|
|
watchpoint_stops = 0
|
|
while True:
|
|
self.runCmd("process continue")
|
|
self.runCmd("process status")
|
|
if re.search("Process .* exited", self.res.GetOutput()):
|
|
# Great, we are done with this test!
|
|
break
|
|
|
|
self.runCmd("thread list")
|
|
if "stop reason = watchpoint" in self.res.GetOutput():
|
|
self.runCmd("thread backtrace all")
|
|
watchpoint_stops += 1
|
|
if watchpoint_stops > 1:
|
|
self.fail("Watchpoint hits not supposed to exceed 1 by design!")
|
|
# Good, we verified that the watchpoint works! Now delete the watchpoint.
|
|
if self.TraceOn():
|
|
print "watchpoint_stops=%d at the moment we delete the watchpoint" % watchpoint_stops
|
|
self.runCmd("watchpoint delete 1")
|
|
self.expect("watchpoint list -v",
|
|
substrs = ['No watchpoints currently set.'])
|
|
continue
|
|
else:
|
|
self.fail("The stop reason should be either break or watchpoint")
|
|
|
|
|
|
if __name__ == '__main__':
|
|
import atexit
|
|
lldb.SBDebugger.Initialize()
|
|
atexit.register(lambda: lldb.SBDebugger.Terminate())
|
|
unittest2.main()
|