c8fd130a2c
Currently most of the test files have a separate dwarf and a separate dsym test with almost identical content (only the build step is different). With adding dwo symbol file handling to the test suit it would increase this to a 3-way duplication. The purpose of this change is to eliminate this redundancy with generating 2 test case (one dwarf and one dsym) for each test function specified (dwo handling will be added at a later commit). Main design goals: * There should be no boilerplate code in each test file to support the multiple debug info in most of the tests (custom scenarios are acceptable in special cases) so adding a new test case is easier and we can't miss one of the debug info type. * In case of a test failure, the debug symbols used during the test run have to be cleanly visible from the output of dotest.py to make debugging easier both from build bot logs and from local test runs * Each test case should have a unique, fully qualified name so we can run exactly 1 test with "-f <test-case>.<test-function>" syntax * Test output should be grouped based on test files the same way as it happens now (displaying dwarf/dsym results separately isn't preferable) Proposed solution (main logic in lldbtest.py, rest of them are test cases fixed up for the new style): * Have only 1 test fuction in the test files what will run for all debug info separately and this test function should call just "self.build(...)" to build an inferior with the right debug info * When a class is created by python (the class object, not the class instance), we will generate a new test method for each debug info format in the test class with the name "<test-function>_<debug-info>" and remove the original test method. This way unittest2 see multiple test methods (1 for each debug info, pretty much as of now) and will handle the test selection and the failure reporting correctly (the debug info will be visible from the end of the test name) * Add new annotation @no_debug_info_test to disable the generation of multiple tests for each debug info format when the test don't have an inferior Differential revision: http://reviews.llvm.org/D13028 llvm-svn: 248883
87 lines
3.2 KiB
Python
87 lines
3.2 KiB
Python
"""
|
|
Test that the lldb driver's batch mode works correctly.
|
|
"""
|
|
|
|
import os, time
|
|
import unittest2
|
|
import lldb
|
|
try:
|
|
import pexpect
|
|
except:
|
|
pexpect = None
|
|
from lldbtest import *
|
|
|
|
class DriverBatchModeTest (TestBase):
|
|
|
|
mydir = TestBase.compute_mydir(__file__)
|
|
|
|
@skipIfRemote # test not remote-ready llvm.org/pr24813
|
|
@expectedFailureWindows("llvm.org/pr22274: need a pexpect replacement for windows")
|
|
def test_driver_batch_mode(self):
|
|
"""Test that the lldb driver's batch mode works correctly."""
|
|
self.build()
|
|
self.setTearDownCleanup()
|
|
self.batch_mode()
|
|
|
|
def setUp(self):
|
|
# Call super's setUp().
|
|
TestBase.setUp(self)
|
|
# Our simple source filename.
|
|
self.source = 'main.c'
|
|
|
|
def expect_string (self, string):
|
|
"""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))
|
|
|
|
def batch_mode (self):
|
|
exe = os.path.join(os.getcwd(), "a.out")
|
|
prompt = "(lldb) "
|
|
|
|
# First time through, pass CRASH so the process will crash and stop in batch mode.
|
|
run_commands = ' -b -o "break set -n main" -o "run" -o "continue" -k "frame var touch_me_not"'
|
|
self.child = pexpect.spawn('%s %s %s %s -- CRASH' % (lldbtest_config.lldbExec, self.lldbOption, run_commands, exe))
|
|
child = self.child
|
|
# Turn on logging for what the child sends back.
|
|
if self.TraceOn():
|
|
child.logfile_read = sys.stdout
|
|
|
|
# We should see the "run":
|
|
self.expect_string ("run")
|
|
# We should have hit the breakpoint & continued:
|
|
self.expect_string ("continue")
|
|
# The App should have crashed:
|
|
self.expect_string("About to crash")
|
|
# The -k option should have printed the frame variable once:
|
|
self.expect_string ('(char *) touch_me_not')
|
|
# Then we should have a live prompt:
|
|
self.expect_string (prompt)
|
|
self.child.sendline("frame variable touch_me_not")
|
|
self.expect_string ('(char *) touch_me_not')
|
|
|
|
self.deletePexpectChild()
|
|
|
|
# Now do it again, and see make sure if we don't crash, we quit:
|
|
run_commands = ' -b -o "break set -n main" -o "run" -o "continue" '
|
|
self.child = pexpect.spawn('%s %s %s %s -- NOCRASH' % (lldbtest_config.lldbExec, self.lldbOption, run_commands, exe))
|
|
child = self.child
|
|
# Turn on logging for what the child sends back.
|
|
if self.TraceOn():
|
|
child.logfile_read = sys.stdout
|
|
|
|
# We should see the "run":
|
|
self.expect_string ("run")
|
|
# We should have hit the breakpoint & continued:
|
|
self.expect_string ("continue")
|
|
# The App should have not have crashed:
|
|
self.expect_string("Got there on time and it did not crash.")
|
|
# Then we should have a live prompt:
|
|
self.expect_string ("exited")
|
|
index = self.child.expect([pexpect.EOF, pexpect.TIMEOUT])
|
|
self.assertTrue(index == 0, "lldb didn't close on successful batch completion.")
|
|
|