c8fd130a2c
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
92 lines
3.7 KiB
Python
92 lines
3.7 KiB
Python
"""
|
|
Test lldb watchpoint that uses 'watchpoint set -w write -s size' to watch a pointed location with size.
|
|
"""
|
|
|
|
import os, time
|
|
import unittest2
|
|
import lldb
|
|
from lldbtest import *
|
|
import lldbutil
|
|
|
|
class WatchLocationUsingWatchpointSetTestCase(TestBase):
|
|
|
|
mydir = TestBase.compute_mydir(__file__)
|
|
|
|
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.line = line_number(self.source, '// Set break point at this line.')
|
|
# This is for verifying that watch location works.
|
|
self.violating_func = "do_bad_thing_with_location";
|
|
# Build dictionary to have unique executable names for each test method.
|
|
|
|
@expectedFailureAndroid(archs=['arm', 'aarch64']) # Watchpoints not supported
|
|
@expectedFailureWindows("llvm.org/pr24446") # WINDOWS XFAIL TRIAGE - Watchpoints not supported on Windows
|
|
def test_watchlocation_using_watchpoint_set(self):
|
|
"""Test watching a location with 'watchpoint set expression -w write -s size' option."""
|
|
self.build()
|
|
self.setTearDownCleanup()
|
|
|
|
exe = os.path.join(os.getcwd(), 'a.out')
|
|
self.runCmd("file " + exe, 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.line, 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 pointed to by 'g_char_ptr' and
|
|
# with offset as 7.
|
|
# The main.cpp, by design, misbehaves by not following the agreed upon
|
|
# protocol of only accessing the allowable index range of [0, 6].
|
|
self.expect("watchpoint set expression -w write -s 1 -- g_char_ptr + 7", WATCHPOINT_CREATED,
|
|
substrs = ['Watchpoint created', 'size = 1', 'type = w'])
|
|
self.runCmd("expr unsigned val = g_char_ptr[7]; val")
|
|
self.expect(self.res.GetOutput().splitlines()[0], exe=False,
|
|
endstr = ' = 0')
|
|
|
|
# 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'])
|
|
|
|
self.runCmd("process continue")
|
|
|
|
# We should be stopped again due to the watchpoint (write type), but
|
|
# only once. The stop reason of the thread should be watchpoint.
|
|
self.expect("thread list", STOPPED_DUE_TO_WATCHPOINT,
|
|
substrs = ['stopped',
|
|
'stop reason = watchpoint',
|
|
self.violating_func])
|
|
|
|
# Switch to the thread stopped due to watchpoint and issue some commands.
|
|
self.switch_to_thread_with_stop_reason(lldb.eStopReasonWatchpoint)
|
|
self.runCmd("thread backtrace")
|
|
self.runCmd("expr unsigned val = g_char_ptr[7]; val")
|
|
self.expect(self.res.GetOutput().splitlines()[0], exe=False,
|
|
endstr = ' = 99')
|
|
|
|
# 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'])
|
|
|
|
self.runCmd("thread backtrace all")
|
|
|
|
|
|
if __name__ == '__main__':
|
|
import atexit
|
|
lldb.SBDebugger.Initialize()
|
|
atexit.register(lambda: lldb.SBDebugger.Terminate())
|
|
unittest2.main()
|