a31130f6fc
Some tests set settings and don't clean them up, this leads to side effects in other tests. The patch removes a global debugger instance with a per-test debugger to avoid such effects. From what I see, lldb.DBG was needed to determine the platform before a test is run, lldb.selected_platform is used for this purpose now. Though, this required adding a new function to the SBPlatform interface. Differential Revision: https://reviews.llvm.org/D74903
29 lines
852 B
Python
29 lines
852 B
Python
import lldb
|
|
from lldbsuite.test.lldbtest import *
|
|
from lldbsuite.test.decorators import *
|
|
from gdbclientutils import *
|
|
|
|
|
|
class TestWriteMemory(GDBRemoteTestBase):
|
|
|
|
def test(self):
|
|
|
|
class MyResponder(MockGDBServerResponder):
|
|
def setBreakpoint(self, packet):
|
|
return "OK"
|
|
|
|
self.server.responder = MyResponder()
|
|
target = self.dbg.CreateTargetWithFileAndTargetTriple('', 'x86_64-pc-linux')
|
|
process = self.connect(target)
|
|
|
|
bp = target.BreakpointCreateByAddress(0x1000)
|
|
self.assertTrue(bp.IsValid())
|
|
self.assertEqual(bp.GetNumLocations(), 1)
|
|
bp.SetEnabled(True)
|
|
self.assertTrue(bp.IsEnabled())
|
|
|
|
err = lldb.SBError()
|
|
data = str("\x01\x02\x03\x04")
|
|
result = process.WriteMemory(0x1000, data, err)
|
|
self.assertEqual(result, 4)
|