102 lines
4.5 KiB
Python
Raw Normal View History

"""
Test lldb target stop-hook mechanism to see whether it fires off correctly .
"""
from __future__ import print_function
import os
import lldb
from lldbsuite.test import configuration
from lldbsuite.test.lldbtest import *
class StopHookMechanismTestCase(TestBase):
mydir = TestBase.compute_mydir(__file__)
def setUp(self):
# Call super's setUp().
TestBase.setUp(self)
# Find the line numbers inside main.cpp.
self.begl = line_number('main.cpp', '// Set breakpoint here to test target stop-hook.')
self.endl = line_number('main.cpp', '// End of the line range for which stop-hook is to be run.')
self.correct_step_line = line_number ('main.cpp', '// We should stop here after stepping.')
self.line = line_number('main.cpp', '// Another breakpoint which is outside of the stop-hook range.')
Merge dwarf and dsym tests 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
2015-09-30 10:12:40 +00:00
@skipIfFreeBSD # 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(self):
"""Test the stop-hook mechanism."""
Merge dwarf and dsym tests 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
2015-09-30 10:12:40 +00:00
self.build()
import pexpect
exe = os.path.join(os.getcwd(), "a.out")
prompt = "(lldb) "
add_prompt = "Enter your stop hook command(s). Type 'DONE' to end."
add_prompt1 = "> "
# 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' % configuration.lldb_platform_url)
child.expect_exact(prompt)
child.sendline('platform settings -w %s' % configuration.lldb_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.begl)
child.expect_exact(prompt)
child.sendline('breakpoint set -f main.cpp -l %d' % self.line)
child.expect_exact(prompt)
child.sendline('target stop-hook add -f main.cpp -l %d -e %d' % (self.begl, self.endl))
child.expect_exact(add_prompt)
child.expect_exact(add_prompt1)
child.sendline('expr ptr')
child.expect_exact(add_prompt1)
child.sendline('DONE')
child.expect_exact(prompt)
child.sendline('target stop-hook list')
# Now run the program, expect to stop at the first breakpoint which is within the stop-hook range.
child.expect_exact(prompt)
child.sendline('run')
# Make sure we see the stop hook text from the stop of the process from the run hitting the first breakpoint
child.expect_exact('(void *) $')
child.expect_exact(prompt)
child.sendline('thread step-over')
# Expecting to find the output emitted by the firing of our stop hook.
child.expect_exact('(void *) $')
# This is orthogonal to the main stop hook test, but this example shows a bug in
# CLANG where the line table entry for the "return -1" actually includes some code
# from the other branch of the if/else, so we incorrectly stop at the "return -1" line.
# I fixed that in lldb and I'm sticking in a test here because I don't want to have to
# make up a whole nother test case for it.
child.sendline('frame info')
at_line = 'at main.cpp:%d' % (self.correct_step_line)
print('expecting "%s"' % at_line)
child.expect_exact(at_line)
# Now continue the inferior, we'll stop at another breakpoint which is outside the stop-hook range.
child.sendline('process continue')
child.expect_exact('// Another breakpoint which is outside of the stop-hook range.')
#self.DebugPExpect(child)
child.sendline('thread step-over')
child.expect_exact('// Another breakpoint which is outside of the stop-hook range.')
#self.DebugPExpect(child)
# Verify that the 'Stop Hooks' mechanism is NOT BEING fired off.
self.expect(child.before, exe=False, matching=False,
substrs = ['(void *) $'])