c15c296521
Nearly all of our lldb-server tests have two flavours (lldb-server and debugserver). Each of them is tagged with an appropriate decorator, and each of them starts with a call to a matching "init" method. The init calls are mandatory, and it's not possible to meaningfully combine them with a different decorator. This patch leverages the existing decorators to also tag the tests with the appropriate debug server tag, similar to how we do with debug info flavours. This allows us to make the "init" calls from inside the common setUp method.
29 lines
996 B
Python
29 lines
996 B
Python
|
|
|
|
import gdbremote_testcase
|
|
from lldbsuite.test.decorators import *
|
|
from lldbsuite.test.lldbtest import *
|
|
from lldbsuite.test import lldbutil
|
|
|
|
|
|
class TestGdbRemoteSingleStep(gdbremote_testcase.GdbRemoteTestCaseBase):
|
|
|
|
mydir = TestBase.compute_mydir(__file__)
|
|
|
|
@skipIfDarwinEmbedded # <rdar://problem/34539270> lldb-server tests not updated to work on ios etc yet
|
|
@debugserver_test
|
|
def test_single_step_only_steps_one_instruction_with_s_debugserver(self):
|
|
self.build()
|
|
self.set_inferior_startup_launch()
|
|
self.single_step_only_steps_one_instruction(
|
|
use_Hc_packet=True, step_instruction="s")
|
|
|
|
@skipIfWindows # No pty support to test any inferior std -i/e/o
|
|
@llgs_test
|
|
@skipIf(triple='^mips')
|
|
def test_single_step_only_steps_one_instruction_with_s_llgs(self):
|
|
self.build()
|
|
self.set_inferior_startup_launch()
|
|
self.single_step_only_steps_one_instruction(
|
|
use_Hc_packet=True, step_instruction="s")
|