summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/expression_command/pr35310/TestExprsBug35310.py
diff options
context:
space:
mode:
authorDavide Italiano <davide@freebsd.org>2018-03-27 19:40:50 +0000
committerDavide Italiano <davide@freebsd.org>2018-03-27 19:40:50 +0000
commit675767a5910d2ec77ef8b51c78fe312cf9022896 (patch)
treec4b7536fb489cb29b04656541fe0971f1c81ca14 /lldb/packages/Python/lldbsuite/test/expression_command/pr35310/TestExprsBug35310.py
parentb130ea5605531640d84753c16b9ad9cab6baa499 (diff)
downloadbcm5719-llvm-675767a5910d2ec77ef8b51c78fe312cf9022896.tar.gz
bcm5719-llvm-675767a5910d2ec77ef8b51c78fe312cf9022896.zip
Use the DWARF linkage name when importing C++ methods.
When importing C++ methods into clang AST nodes from the DWARF symbol table, preserve the DW_AT_linkage_name and use it as the linker ("asm") name for the symbol. Concretely, this enables `expression` to call into names that use the GNU `abi_tag` extension, and enables lldb to call into code using std::string or std::list from recent versions of libstdc++. See https://bugs.llvm.org/show_bug.cgi?id=35310 . It also seems broadly more robust than relying on the DWARF->clang->codegen pipeline to roundtrip properly, but I'm not immediately aware of any other cases in which it makes a difference. Patch by Nelson Elhage! Differential Revision: https://reviews.llvm.org/D40283 llvm-svn: 328658
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/expression_command/pr35310/TestExprsBug35310.py')
-rw-r--r--lldb/packages/Python/lldbsuite/test/expression_command/pr35310/TestExprsBug35310.py39
1 files changed, 39 insertions, 0 deletions
diff --git a/lldb/packages/Python/lldbsuite/test/expression_command/pr35310/TestExprsBug35310.py b/lldb/packages/Python/lldbsuite/test/expression_command/pr35310/TestExprsBug35310.py
new file mode 100644
index 00000000000..6cc479401de
--- /dev/null
+++ b/lldb/packages/Python/lldbsuite/test/expression_command/pr35310/TestExprsBug35310.py
@@ -0,0 +1,39 @@
+from __future__ import print_function
+
+import lldb
+from lldbsuite.test.decorators import *
+from lldbsuite.test.lldbtest import *
+from lldbsuite.test import lldbutil
+
+class ExprBug35310(TestBase):
+
+ mydir = TestBase.compute_mydir(__file__)
+
+ def setUp(self):
+ # Call super's setUp().
+ TestBase.setUp(self)
+
+ self.main_source = "main.cpp"
+ self.main_source_spec = lldb.SBFileSpec(self.main_source)
+
+ def test_issue35310(self):
+ """Test invoking functions with non-standard linkage names.
+
+ The GNU abi_tag extension used by libstdc++ is a common source
+ of these, but they could originate from other reasons as well.
+ """
+ self.build()
+
+ (target, process, thread, bkpt) = lldbutil.run_to_source_breakpoint(self,
+ '// Break here', self.main_source_spec)
+ frame = thread.GetFrameAtIndex(0)
+
+ value = frame.EvaluateExpression("a.test_abi_tag()")
+ self.assertTrue(value.IsValid())
+ self.assertTrue(value.GetError().Success())
+ self.assertEqual(value.GetValueAsSigned(0), 1)
+
+ value = frame.EvaluateExpression("a.test_asm_name()")
+ self.assertTrue(value.IsValid())
+ self.assertTrue(value.GetError().Success())
+ self.assertEqual(value.GetValueAsSigned(0), 2)
OpenPOWER on IntegriCloud