llvm-project/lldb/packages/Python/lldbsuite/test/lang/cpp/scope/TestCppScope.py

99 lines
3.2 KiB
Python
Raw Normal View History

"""
Test scopes in C++.
"""
import lldb
from lldbsuite.test.decorators import *
from lldbsuite.test.lldbtest import *
from lldbsuite.test import lldbutil
class TestCppScopes(TestBase):
mydir = TestBase.compute_mydir(__file__)
@expectedFailureAll(oslist=["windows"], bugnumber="llvm.org/pr24764")
def test_all_but_c(self):
self.do_test(False)
# There's a global symbol in libsystem on Darwin that messes up
# the lookup of class C. Breaking that test out from the others
# since that is a odd failure, and I don't want it to mask the
# real purpose of this test.
@expectedFailureDarwin(bugnumber="<rdar://problem/28623427>")
@expectedFailureAll(oslist=["windows"])
def test_c(self):
self.do_test(True)
def do_test(self, test_c):
Merge dwarf and dsym tests 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
2015-09-30 18:12:40 +08:00
self.build()
# Get main source file
src_file = "main.cpp"
src_file_spec = lldb.SBFileSpec(src_file)
self.assertTrue(src_file_spec.IsValid(), "Main source file")
# Get the path of the executable
cwd = os.getcwd()
exe_file = "a.out"
exe_path = os.path.join(cwd, exe_file)
# Load the executable
target = self.dbg.CreateTarget(exe_path)
self.assertTrue(target.IsValid(), VALID_TARGET)
# Break on main function
main_breakpoint = target.BreakpointCreateBySourceRegex(
"// break here", src_file_spec)
self.assertTrue(
main_breakpoint.IsValid() and main_breakpoint.GetNumLocations() >= 1,
VALID_BREAKPOINT)
# Launch the process
args = None
env = None
process = target.LaunchSimple(
args, env, self.get_process_working_directory())
self.assertTrue(process.IsValid(), PROCESS_IS_VALID)
# Get the thread of the process
self.assertTrue(
process.GetState() == lldb.eStateStopped,
PROCESS_STOPPED)
thread = lldbutil.get_stopped_thread(
process, lldb.eStopReasonBreakpoint)
# Get current fream of the thread at the breakpoint
frame = thread.GetSelectedFrame()
# Test result for scopes of variables
global_variables = frame.GetVariables(True, True, True, False)
global_variables_assert = {
'A::a': 1111,
'B::a': 2222,
'C::a': 3333,
'::a': 4444,
'a': 4444
}
self.assertTrue(
global_variables.GetSize() == 4,
"target variable returns all variables")
for variable in global_variables:
name = variable.GetName()
self.assertTrue(
name in global_variables_assert,
"target variable returns wrong variable " + name)
for name in global_variables_assert:
if name is "C::a" and not test_c:
continue
if name is not "C::a" and test_c:
continue
value = frame.EvaluateExpression(name)
assert_value = global_variables_assert[name]
self.assertTrue(
value.IsValid() and value.GetValueAsSigned() == assert_value,
name + " = " + str(assert_value))