summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/expression_command/multiline-completion/TestMultilineCompletion.py
diff options
context:
space:
mode:
authorRaphael Isemann <teemperor@gmail.com>2019-07-30 12:31:24 +0000
committerRaphael Isemann <teemperor@gmail.com>2019-07-30 12:31:24 +0000
commite010f6bab39f76cfbb0b4dc1c0d4700b078c53e3 (patch)
tree4e5db894dd39772429d13a4a81ef8afeca5941cc /lldb/packages/Python/lldbsuite/test/expression_command/multiline-completion/TestMultilineCompletion.py
parent3e85b6f3bd7775a83d5880e0087cb5f434c12626 (diff)
downloadbcm5719-llvm-e010f6bab39f76cfbb0b4dc1c0d4700b078c53e3.tar.gz
bcm5719-llvm-e010f6bab39f76cfbb0b4dc1c0d4700b078c53e3.zip
[lldb] Fix crash when tab-completing in multi-line expr
Summary: Tab completing inside the multiline expression command can cause LLDB to crash. The easiest way to do this is to go inside a frame with at least one local variable and then try to complete: (lldb) expr 1. a[tab] Reason for this was some mixup when we calculate the cursor position. Obviously we should calculate the offset inside the string by doing 'end - start', but we are doing 'start - end' (which causes the offset to become -1 which will lead to some out-of-bounds reading). Fixes rdar://51754005 I don't see any way to test this as the *multiline* expression completion is completely untested at the moment and I don't think we have any existing code for testing infrastructure for it. Reviewers: shafik, davide, labath Reviewed By: labath Subscribers: abidh, lldb-commits, davide, clayborg, labath Tags: #lldb Differential Revision: https://reviews.llvm.org/D64995 llvm-svn: 367308
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/expression_command/multiline-completion/TestMultilineCompletion.py')
-rw-r--r--lldb/packages/Python/lldbsuite/test/expression_command/multiline-completion/TestMultilineCompletion.py52
1 files changed, 52 insertions, 0 deletions
diff --git a/lldb/packages/Python/lldbsuite/test/expression_command/multiline-completion/TestMultilineCompletion.py b/lldb/packages/Python/lldbsuite/test/expression_command/multiline-completion/TestMultilineCompletion.py
new file mode 100644
index 00000000000..2d75fc471d5
--- /dev/null
+++ b/lldb/packages/Python/lldbsuite/test/expression_command/multiline-completion/TestMultilineCompletion.py
@@ -0,0 +1,52 @@
+"""
+Test completion for multiline expressions.
+"""
+
+import lldb
+from lldbsuite.test.decorators import *
+from lldbsuite.test.lldbtest import *
+
+class MultilineCompletionTest(TestBase):
+
+ mydir = TestBase.compute_mydir(__file__)
+ NO_DEBUG_INFO_TESTCASE = True
+
+ def setUp(self):
+ TestBase.setUp(self)
+ self.source = 'main.c'
+
+ def expect_string(self, string):
+ import pexpect
+ """This expects for "string", with timeout & EOF being test fails."""
+ try:
+ self.child.expect_exact(string)
+ except pexpect.EOF:
+ self.fail("Got EOF waiting for '%s'" % (string))
+ except pexpect.TIMEOUT:
+ self.fail("Timed out waiting for '%s'" % (string))
+
+ @expectedFailureAll(
+ oslist=["windows"],
+ bugnumber="llvm.org/pr22274: need a pexpect replacement for windows")
+ def test_basic_completion(self):
+ """Test that we can complete a simple multiline expression"""
+ self.build()
+ self.setTearDownCleanup()
+
+ import pexpect
+ exe = self.getBuildArtifact("a.out")
+ prompt = "(lldb) "
+
+ run_commands = ' -o "b main" -o "r"'
+ self.child = pexpect.spawn(
+ '%s %s %s %s' %
+ (lldbtest_config.lldbExec, self.lldbOption, run_commands, exe))
+ child = self.child
+
+ self.expect_string(prompt)
+ self.child.sendline("expr")
+ self.expect_string("terminate with an empty line to evaluate")
+ self.child.send("to_\t")
+ self.expect_string("to_complete")
+
+ self.deletePexpectChild()
OpenPOWER on IntegriCloud