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
81 lines
3.2 KiB
Python
81 lines
3.2 KiB
Python
"""
|
|
Test that lldb stop-hook works for multiple threads.
|
|
"""
|
|
|
|
import os, time
|
|
import unittest2
|
|
import lldb
|
|
from lldbtest import *
|
|
|
|
class StopHookForMultipleThreadsTestCase(TestBase):
|
|
|
|
mydir = TestBase.compute_mydir(__file__)
|
|
|
|
def setUp(self):
|
|
# Call super's setUp().
|
|
TestBase.setUp(self)
|
|
# Our simple source filename.
|
|
self.source = 'main.cpp'
|
|
# Find the line number to break inside main().
|
|
self.first_stop = line_number(self.source, '// Set break point at this line, and add a stop-hook.')
|
|
self.thread_function = line_number(self.source, '// Break here to test that the stop-hook mechanism works for multiple threads.')
|
|
# Build dictionary to have unique executable names for each test method.
|
|
self.exe_name = self.testMethodName
|
|
self.d = {'CXX_SOURCES': self.source, 'EXE': self.exe_name}
|
|
|
|
@expectedFlakeyFreeBSD("llvm.org/pr15037")
|
|
@expectedFlakeyLinux("llvm.org/pr15037") # stop hooks sometimes fail to fire on Linux
|
|
@expectedFailureHostWindows("llvm.org/pr22274: need a pexpect replacement for windows")
|
|
def test_stop_hook_multiple_threads(self):
|
|
"""Test that lldb stop-hook works for multiple threads."""
|
|
self.build(dictionary=self.d)
|
|
self.setTearDownCleanup(dictionary=self.d)
|
|
|
|
import pexpect
|
|
exe = os.path.join(os.getcwd(), self.exe_name)
|
|
prompt = "(lldb) "
|
|
|
|
# So that the child gets torn down after the test.
|
|
self.child = pexpect.spawn('%s %s' % (lldbtest_config.lldbExec, self.lldbOption))
|
|
child = self.child
|
|
# Turn on logging for what the child sends back.
|
|
if self.TraceOn():
|
|
child.logfile_read = sys.stdout
|
|
|
|
if lldb.remote_platform:
|
|
child.expect_exact(prompt)
|
|
child.sendline('platform select %s' % lldb.remote_platform.GetName())
|
|
child.expect_exact(prompt)
|
|
child.sendline('platform connect %s' % lldb.platform_url)
|
|
child.expect_exact(prompt)
|
|
child.sendline('platform settings -w %s' % lldb.remote_platform_working_dir)
|
|
|
|
child.expect_exact(prompt)
|
|
child.sendline('target create %s' % exe)
|
|
|
|
# Set the breakpoint, followed by the target stop-hook commands.
|
|
child.expect_exact(prompt)
|
|
child.sendline('breakpoint set -f main.cpp -l %d' % self.first_stop)
|
|
child.expect_exact(prompt)
|
|
child.sendline('breakpoint set -f main.cpp -l %d' % self.thread_function)
|
|
child.expect_exact(prompt)
|
|
|
|
# Now run the program, expect to stop at the first breakpoint which is within the stop-hook range.
|
|
child.sendline('run')
|
|
child.expect_exact("Process") # 'Process 2415 launched', 'Process 2415 stopped'
|
|
child.expect_exact(prompt)
|
|
child.sendline('target stop-hook add -o "frame variable --show-globals g_val"')
|
|
child.expect_exact("Stop hook") # 'Stop hook #1 added.'
|
|
child.expect_exact(prompt)
|
|
|
|
# Continue and expect to find the output emitted by the firing of our stop hook.
|
|
child.sendline('continue')
|
|
child.expect_exact('(uint32_t) ::g_val = ')
|
|
|
|
|
|
if __name__ == '__main__':
|
|
import atexit
|
|
lldb.SBDebugger.Initialize()
|
|
atexit.register(lambda: lldb.SBDebugger.Terminate())
|
|
unittest2.main()
|