1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
|
from lldbsuite.test.decorators import *
from lldbsuite.test.lldbtest import *
from lldbsuite.test import lldbutil
class TestCase(TestBase):
mydir = TestBase.compute_mydir(__file__)
@add_test_categories(["libc++"])
@skipIf(compiler=no_match("clang"))
def test(self):
self.build()
lldbutil.run_to_source_breakpoint(self,
"// Set break point at this line.",
lldb.SBFileSpec("main.cpp"))
# Test printing the vector before enabling any C++ module setting.
self.expect_expr("a", result_type="std::vector<int, std::allocator<int> >")
# Set loading the import-std-module to 'fallback' which loads the module
# and retries when an expression fails to parse.
self.runCmd("settings set target.import-std-module fallback")
# Printing the vector still works. This should return the same type
# as before as this shouldn't use a C++ module type (the C++ module type
# is hiding the second template parameter as it's equal to the default
# argument which the C++ module has type info for).
self.expect_expr("a", result_type="std::vector<int, std::allocator<int> >")
# This expression can only parse with a C++ module. LLDB should
# automatically fall back to import the C++ module to get this working.
self.expect_expr("std::max<std::size_t>(0U, a.size())", result_value="3")
# The 'a' and 'local' part can be parsed without loading a C++ module and will
# load type/runtime information. The 'std::max...' part will fail to
# parse without a C++ module. Make sure we reset all the relevant parts of
# the C++ parser so that we don't end up with for example a second
# definition of 'local' when retrying.
self.expect_expr("a; local; std::max<std::size_t>(0U, a.size())", result_value="3")
# Try to declare top-level declarations that require a C++ module to parse.
# Top-level expressions don't support importing the C++ module (yet), so
# this should still fail as before.
self.expect("expr --top-level -- int i = std::max(1, 2);", error=True,
substrs=["no member named 'max' in namespace 'std'"])
# Check that diagnostics from the first parse attempt don't show up
# in the C++ module parse attempt. In the expression below, we first
# fail to parse 'std::max'. Then we retry with a loaded C++ module
# and succeed to parse the 'std::max' part. However, the
# trailing 'unknown_identifier' will fail to parse even with the
# loaded module. The 'std::max' diagnostic from the first attempt
# however should not be shown to the user.
self.expect("expr std::max(1, 2); unknown_identifier", error=True,
matching=False,
substrs=["no member named 'max'"])
# The proper diagnostic however should be shown on the retry.
self.expect("expr std::max(1, 2); unknown_identifier", error=True,
substrs=["use of undeclared identifier 'unknown_identifier'"])
# Turn on the 'import-std-module' setting and make sure we import the
# C++ module.
self.runCmd("settings set target.import-std-module true")
# This is still expected to work.
self.expect_expr("std::max<std::size_t>(0U, a.size())", result_value="3")
# Turn of the 'import-std-module' setting and make sure we don't load
# the module (which should prevent parsing the expression involving
# 'std::max').
self.runCmd("settings set target.import-std-module false")
self.expect("expr std::max(1, 2);", error=True,
substrs=["no member named 'max' in namespace 'std'"])
|
