4570d3eba0
This has led to many test suite failures because of copy and paste where new test cases were based off of other test cases and the "mydir" variable wasn't updated. Now you can call your superclasses "compute_mydir()" function with "__file__" as the sole argument and the relative path will be computed for you. llvm-svn: 196985
74 lines
2.5 KiB
Python
74 lines
2.5 KiB
Python
"""
|
|
Tests that rvalue references are supported in C++
|
|
"""
|
|
|
|
import lldb
|
|
from lldbtest import *
|
|
import lldbutil
|
|
|
|
class RvalueReferencesTestCase(TestBase):
|
|
|
|
mydir = TestBase.compute_mydir(__file__)
|
|
|
|
@unittest2.skipUnless(sys.platform.startswith("darwin"), "requires Darwin")
|
|
#rdar://problem/11479676
|
|
@expectedFailureClang
|
|
@dsym_test
|
|
def test_with_dsym_and_run_command(self):
|
|
"""Test that rvalues are supported in the C++ expression parser"""
|
|
self.buildDsym()
|
|
self.static_method_commands()
|
|
|
|
#rdar://problem/11479676
|
|
@expectedFailureClang # pr16762: Expression evaluation of an rvalue-reference does not show the correct type.
|
|
@expectedFailureGcc # GCC (4.7) does not emit correct DWARF tags for rvalue-references
|
|
@expectedFailureIcc # ICC (13.1, 14-beta) do not emit DW_TAG_rvalue_reference_type.
|
|
@dwarf_test
|
|
def test_with_dwarf_and_run_command(self):
|
|
"""Test that rvalues are supported in the C++ expression parser"""
|
|
self.buildDwarf()
|
|
self.static_method_commands()
|
|
|
|
def setUp(self):
|
|
TestBase.setUp(self)
|
|
|
|
def set_breakpoint(self, line):
|
|
lldbutil.run_break_set_by_file_and_line (self, "main.cpp", line, num_expected_locations=1, loc_exact=True)
|
|
|
|
def static_method_commands(self):
|
|
"""Test that rvalues are supported in the C++ expression parser"""
|
|
self.runCmd("file a.out", CURRENT_EXECUTABLE_SET)
|
|
|
|
self.set_breakpoint(line_number('main.cpp', '// breakpoint 1'))
|
|
self.set_breakpoint(line_number('main.cpp', '// breakpoint 2'))
|
|
|
|
self.runCmd("process launch", RUN_SUCCEEDED)
|
|
|
|
# Note that clang as of r187480 doesn't emit DW_TAG_const_type, unlike gcc 4.8.1
|
|
# With gcc 4.8.1, lldb reports the type as (int &&const)
|
|
self.expect("frame variable i",
|
|
startstr = "(int &&",
|
|
substrs = ["i = 0x", "&i = 3"])
|
|
|
|
self.expect("expression -- i",
|
|
startstr = "(int &&",
|
|
substrs = ["3"])
|
|
|
|
self.expect("breakpoint delete 1")
|
|
|
|
self.runCmd("process continue")
|
|
|
|
self.expect("expression -- foo(2)")
|
|
|
|
self.expect("expression -- int &&j = 3; foo(j)",
|
|
error = True)
|
|
|
|
self.expect("expression -- int &&k = 6; k",
|
|
startstr = "(int) $1 = 6")
|
|
|
|
if __name__ == '__main__':
|
|
import atexit
|
|
lldb.SBDebugger.Initialize()
|
|
atexit.register(lambda: lldb.SBDebugger.Terminate())
|
|
unittest2.main()
|