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
148 lines
5.9 KiB
Python
148 lines
5.9 KiB
Python
"""Test Python APIs for target (launch and attach), breakpoint, and process."""
|
|
|
|
import os, sys, time
|
|
import unittest2
|
|
import lldb
|
|
import time
|
|
from lldbtest import *
|
|
|
|
class HelloWorldTestCase(TestBase):
|
|
|
|
mydir = TestBase.compute_mydir(__file__)
|
|
|
|
def setUp(self):
|
|
# Call super's setUp().
|
|
TestBase.setUp(self)
|
|
# Get the full path to our executable to be attached/debugged.
|
|
self.exe = os.path.join(os.getcwd(), self.testMethodName)
|
|
self.d = {'EXE': self.testMethodName}
|
|
# Find a couple of the line numbers within main.c.
|
|
self.line1 = line_number('main.c', '// Set break point at this line.')
|
|
self.line2 = line_number('main.c', '// Waiting to be attached...')
|
|
|
|
def tearDown(self):
|
|
# Destroy process before TestBase.tearDown()
|
|
self.dbg.GetSelectedTarget().GetProcess().Destroy()
|
|
# Call super's tearDown().
|
|
TestBase.tearDown(self)
|
|
|
|
@python_api_test
|
|
def test_with_process_launch_api(self):
|
|
"""Create target, breakpoint, launch a process, and then kill it."""
|
|
self.build(dictionary=self.d)
|
|
self.setTearDownCleanup(dictionary=self.d)
|
|
target = self.dbg.CreateTarget(self.exe)
|
|
|
|
breakpoint = target.BreakpointCreateByLocation("main.c", self.line1)
|
|
|
|
# The default state after breakpoint creation should be enabled.
|
|
self.assertTrue(breakpoint.IsEnabled(),
|
|
"Breakpoint should be enabled after creation")
|
|
|
|
breakpoint.SetEnabled(False)
|
|
self.assertTrue(not breakpoint.IsEnabled(),
|
|
"Breakpoint.SetEnabled(False) works")
|
|
|
|
breakpoint.SetEnabled(True)
|
|
self.assertTrue(breakpoint.IsEnabled(),
|
|
"Breakpoint.SetEnabled(True) works")
|
|
|
|
# rdar://problem/8364687
|
|
# SBTarget.Launch() issue (or is there some race condition)?
|
|
|
|
process = target.LaunchSimple (None, None, self.get_process_working_directory())
|
|
# The following isn't needed anymore, rdar://8364687 is fixed.
|
|
#
|
|
# Apply some dances after LaunchProcess() in order to break at "main".
|
|
# It only works sometimes.
|
|
#self.breakAfterLaunch(process, "main")
|
|
|
|
process = target.GetProcess()
|
|
self.assertTrue(process, PROCESS_IS_VALID)
|
|
|
|
thread = process.GetThreadAtIndex(0)
|
|
if thread.GetStopReason() != lldb.eStopReasonBreakpoint:
|
|
from lldbutil import stop_reason_to_str
|
|
self.fail(STOPPED_DUE_TO_BREAKPOINT_WITH_STOP_REASON_AS %
|
|
stop_reason_to_str(thread.GetStopReason()))
|
|
|
|
# The breakpoint should have a hit count of 1.
|
|
self.assertTrue(breakpoint.GetHitCount() == 1, BREAKPOINT_HIT_ONCE)
|
|
|
|
@python_api_test
|
|
@expectedFailurei386 # llvm.org/pr17384: lldb needs to be aware of linux-vdso.so to unwind stacks properly
|
|
@expectedFailureWindows("llvm.org/pr24600")
|
|
def test_with_attach_to_process_with_id_api(self):
|
|
"""Create target, spawn a process, and attach to it with process id."""
|
|
self.build(dictionary=self.d)
|
|
self.setTearDownCleanup(dictionary=self.d)
|
|
target = self.dbg.CreateTarget(self.exe)
|
|
|
|
# Spawn a new process
|
|
popen = self.spawnSubprocess(self.exe, ["abc", "xyz"])
|
|
self.addTearDownHook(self.cleanupSubprocesses)
|
|
|
|
# Give the subprocess time to start and wait for user input
|
|
time.sleep(0.25)
|
|
|
|
listener = lldb.SBListener("my.attach.listener")
|
|
error = lldb.SBError()
|
|
process = target.AttachToProcessWithID(listener, popen.pid, error)
|
|
|
|
self.assertTrue(error.Success() and process, PROCESS_IS_VALID)
|
|
|
|
# Let's check the stack traces of the attached process.
|
|
import lldbutil
|
|
stacktraces = lldbutil.print_stacktraces(process, string_buffer=True)
|
|
self.expect(stacktraces, exe=False,
|
|
substrs = ['main.c:%d' % self.line2,
|
|
'(int)argc=3'])
|
|
|
|
@python_api_test
|
|
@expectedFailurei386 # llvm.org/pr17384: lldb needs to be aware of linux-vdso.so to unwind stacks properly
|
|
@expectedFailureWindows("llvm.org/pr24600")
|
|
def test_with_attach_to_process_with_name_api(self):
|
|
"""Create target, spawn a process, and attach to it with process name."""
|
|
self.build(dictionary=self.d)
|
|
self.setTearDownCleanup(dictionary=self.d)
|
|
target = self.dbg.CreateTarget(self.exe)
|
|
|
|
# Spawn a new process
|
|
popen = self.spawnSubprocess(self.exe, ["abc", "xyz"])
|
|
self.addTearDownHook(self.cleanupSubprocesses)
|
|
|
|
# Give the subprocess time to start and wait for user input
|
|
time.sleep(0.25)
|
|
|
|
listener = lldb.SBListener("my.attach.listener")
|
|
error = lldb.SBError()
|
|
# Pass 'False' since we don't want to wait for new instance of "hello_world" to be launched.
|
|
name = os.path.basename(self.exe)
|
|
|
|
# While we're at it, make sure that passing a None as the process name
|
|
# does not hang LLDB.
|
|
target.AttachToProcessWithName(listener, None, False, error)
|
|
# Also boundary condition test ConnectRemote(), too.
|
|
target.ConnectRemote(listener, None, None, error)
|
|
|
|
process = target.AttachToProcessWithName(listener, name, False, error)
|
|
|
|
self.assertTrue(error.Success() and process, PROCESS_IS_VALID)
|
|
|
|
# Verify that after attach, our selected target indeed matches name.
|
|
self.expect(self.dbg.GetSelectedTarget().GetExecutable().GetFilename(), exe=False,
|
|
startstr = name)
|
|
|
|
# Let's check the stack traces of the attached process.
|
|
import lldbutil
|
|
stacktraces = lldbutil.print_stacktraces(process, string_buffer=True)
|
|
self.expect(stacktraces, exe=False,
|
|
substrs = ['main.c:%d' % self.line2,
|
|
'(int)argc=3'])
|
|
|
|
if __name__ == '__main__':
|
|
import atexit
|
|
lldb.SBDebugger.Initialize()
|
|
atexit.register(lambda: lldb.SBDebugger.Terminate())
|
|
unittest2.main()
|