mirror of
https://github.com/Gericom/teak-llvm.git
synced 2025-06-22 04:55:50 -04:00
95c453a221
For convenience, we had added the folder that dotest.py was in to sys.path, so that we could easily write things like `import lldbutil` from anywhere and any test. This introduces a subtle problem when using Python's package system, because when unittest2 imports a particular test suite, the test suite is detached from the package. Thus, writing "import lldbutil" from dotest imports it as part of the package, and writing the same line from a test does a fresh import since the importing module was not part of the same package. The real way to fix this is to use absolute imports everywhere. Instead of writing "import lldbutil", we need to write "import lldbsuite.test.util". This patch fixes up that and all other similar cases, and additionally removes the script directory from sys.path to ensure that this can't happen again. llvm-svn: 251886
112 lines
4.4 KiB
Python
112 lines
4.4 KiB
Python
"""
|
|
Test the printing of anonymous and named namespace variables.
|
|
"""
|
|
|
|
from __future__ import print_function
|
|
|
|
import use_lldb_suite
|
|
|
|
import os, time
|
|
import lldb
|
|
from lldbsuite.test.lldbtest import *
|
|
import lldbsuite.test.lldbutil as lldbutil
|
|
|
|
class NamespaceTestCase(TestBase):
|
|
|
|
mydir = TestBase.compute_mydir(__file__)
|
|
|
|
def setUp(self):
|
|
# Call super's setUp().
|
|
TestBase.setUp(self)
|
|
# Find the line numbers for declarations of namespace variables i and j.
|
|
self.line_var_i = line_number('main.cpp',
|
|
'// Find the line number for anonymous namespace variable i.')
|
|
self.line_var_j = line_number('main.cpp',
|
|
'// Find the line number for named namespace variable j.')
|
|
# And the line number to break at.
|
|
self.line_break = line_number('main.cpp',
|
|
'// Set break point at this line.')
|
|
|
|
# rdar://problem/8668674
|
|
@expectedFailureWindows("llvm.org/pr24764")
|
|
def test_with_run_command(self):
|
|
"""Test that anonymous and named namespace variables display correctly."""
|
|
self.build()
|
|
self.runCmd("file a.out", CURRENT_EXECUTABLE_SET)
|
|
|
|
lldbutil.run_break_set_by_file_and_line (self, "main.cpp", self.line_break, num_expected_locations=1, loc_exact=True)
|
|
|
|
self.runCmd("run", RUN_SUCCEEDED)
|
|
|
|
# The stop reason of the thread should be breakpoint.
|
|
self.expect("thread list", STOPPED_DUE_TO_BREAKPOINT,
|
|
substrs = ['stopped',
|
|
'stop reason = breakpoint'])
|
|
|
|
# On Mac OS X, gcc 4.2 emits the wrong debug info with respect to types.
|
|
slist = ['(int) a = 12', 'anon_uint', 'a_uint', 'b_uint', 'y_uint']
|
|
if self.platformIsDarwin() and self.getCompiler() in ['clang', 'llvm-gcc']:
|
|
slist = ['(int) a = 12',
|
|
'::my_uint_t', 'anon_uint = 0',
|
|
'(A::uint_t) a_uint = 1',
|
|
'(A::B::uint_t) b_uint = 2',
|
|
'(Y::uint_t) y_uint = 3']
|
|
|
|
# 'frame variable' displays the local variables with type information.
|
|
self.expect('frame variable', VARIABLES_DISPLAYED_CORRECTLY,
|
|
substrs = slist)
|
|
|
|
# 'frame variable' with basename 'i' should work.
|
|
self.expect("frame variable --show-declaration --show-globals i",
|
|
startstr = "main.cpp:%d: (int) (anonymous namespace)::i = 3" % self.line_var_i)
|
|
# main.cpp:12: (int) (anonymous namespace)::i = 3
|
|
|
|
# 'frame variable' with basename 'j' should work, too.
|
|
self.expect("frame variable --show-declaration --show-globals j",
|
|
startstr = "main.cpp:%d: (int) A::B::j = 4" % self.line_var_j)
|
|
# main.cpp:19: (int) A::B::j = 4
|
|
|
|
# 'frame variable' should support address-of operator.
|
|
self.runCmd("frame variable &i")
|
|
|
|
# 'frame variable' with fully qualified name 'A::B::j' should work.
|
|
self.expect("frame variable A::B::j", VARIABLES_DISPLAYED_CORRECTLY,
|
|
startstr = '(int) A::B::j = 4',
|
|
patterns = [' = 4'])
|
|
|
|
# So should the anonymous namespace case.
|
|
self.expect("frame variable '(anonymous namespace)::i'", VARIABLES_DISPLAYED_CORRECTLY,
|
|
startstr = '(int) (anonymous namespace)::i = 3',
|
|
patterns = [' = 3'])
|
|
|
|
# rdar://problem/8660275
|
|
# test/namespace: 'expression -- i+j' not working
|
|
# This has been fixed.
|
|
self.expect("expression -- i + j",
|
|
startstr = "(int) $0 = 7")
|
|
# (int) $0 = 7
|
|
|
|
self.runCmd("expression -- i")
|
|
self.runCmd("expression -- j")
|
|
|
|
# rdar://problem/8668674
|
|
# expression command with fully qualified namespace for a variable does not work
|
|
self.expect("expression -- ::i", VARIABLES_DISPLAYED_CORRECTLY,
|
|
patterns = [' = 3'])
|
|
self.expect("expression -- A::B::j", VARIABLES_DISPLAYED_CORRECTLY,
|
|
patterns = [' = 4'])
|
|
|
|
# expression command with function in anonymous namespace
|
|
self.expect("expression -- myanonfunc(3)",
|
|
patterns = [' = 6'])
|
|
|
|
# global namespace qualification with function in anonymous namespace
|
|
self.expect("expression -- ::myanonfunc(4)",
|
|
patterns = [' = 8'])
|
|
|
|
self.expect("p myanonfunc",
|
|
patterns = ['\(anonymous namespace\)::myanonfunc\(int\)'])
|
|
|
|
self.expect("p variadic_sum",
|
|
patterns = ['\(anonymous namespace\)::variadic_sum\(int, ...\)'])
|