[lldb][tests] Automatically call compute_mydir (NFC)Eliminate boilerplate of having each test manually assign to `mydir` by calling`compute_mydir` in lldbtest.py.Differential Revision: https://r
[lldb][tests] Automatically call compute_mydir (NFC)Eliminate boilerplate of having each test manually assign to `mydir` by calling`compute_mydir` in lldbtest.py.Differential Revision: https://reviews.llvm.org/D128077
show more ...
[LLDB] Testsuite: Add helper to check for AArch64 targetThis patch adds a helper function to test target architecture isAArch64 or not. This also tightens isAArch64* helpers by adding anextra arc
[LLDB] Testsuite: Add helper to check for AArch64 targetThis patch adds a helper function to test target architecture isAArch64 or not. This also tightens isAArch64* helpers by adding anextra architecture check.Reviewed By: DavidSpickettDifferential Revision: https://reviews.llvm.org/D105483
[lldb] Convert assertTrue(a == b) to assertEqual(a, b)Convert `assertTrue(a == b)` to `assertEqual(a, b)` to produce better failure messages.These were mostly done via regex search & replace, wit
[lldb] Convert assertTrue(a == b) to assertEqual(a, b)Convert `assertTrue(a == b)` to `assertEqual(a, b)` to produce better failure messages.These were mostly done via regex search & replace, with some manual fixes.Differential Revision: https://reviews.llvm.org/D95813
[Process/NetBSD] Copy changes from FreeBSDRemote and reformatCopy changes, including:- NativeProcessNetBSD::GetLoadedModuleFileSpec() and NativeProcessNetBSD::GetFileLoadAddress() methods- sp
[Process/NetBSD] Copy changes from FreeBSDRemote and reformatCopy changes, including:- NativeProcessNetBSD::GetLoadedModuleFileSpec() and NativeProcessNetBSD::GetFileLoadAddress() methods- split x86 register sets by CPU extensions- use offset/size-based register reading/writingDifferential Revision: https://reviews.llvm.org/D93541
[lldb/test] Reduce boilerplate in lldb-server testsNearly all of our lldb-server tests have two flavours (lldb-server anddebugserver). Each of them is tagged with an appropriate decorator, andeac
[lldb/test] Reduce boilerplate in lldb-server testsNearly all of our lldb-server tests have two flavours (lldb-server anddebugserver). Each of them is tagged with an appropriate decorator, andeach of them starts with a call to a matching "init" method. The initcalls are mandatory, and it's not possible to meaningfully combine themwith a different decorator.This patch leverages the existing decorators to also tag the tests withthe appropriate debug server tag, similar to how we do with debug infoflavours. This allows us to make the "init" calls from inside the commonsetUp method.
Make offset field optional in RegisterInfo packet for Arm64This patch carries forward our aim to remove offset field from qRegisterInfopackets and XML register description. I have created a new fu
Make offset field optional in RegisterInfo packet for Arm64This patch carries forward our aim to remove offset field from qRegisterInfopackets and XML register description. I have created a new function whichreturns if offset fields are dynamic meaning client can calculate offset onits own based on register number sequence and register size. For now thisfunction only returns true for NativeRegisterContextLinux_arm64 but we cantest this for other architectures and make it standard later.As a consequence we do not send offset field from lldb-server (arm64 for now)while other stubs dont have an offset field so it wont effect them for now.On the client side we have replaced previous offset calculation algorithmwith a new scheme, where we sort all primary registers in increasingorder of remote regnum and then calculate offset incrementally.This committ also includes a test to verify all of above functionalityon Arm64.Reviewed By: labathDifferential Revision: https://reviews.llvm.org/D91241
[lldb/Test] Use self.assertIn in TestGdbRemoteTargetXmlPacketOn the ARM buildbot the returned architecture is `armv8l` whilegetArchitecture() just returns `arm`.
[lldb][test] Move registers-target-xml-reading target to the correct test location.This test was added in D74217 (and the `.categories` file later added in ccf1c30cde6e1e763e7c9cdd48a609a805166699)
[lldb][test] Move registers-target-xml-reading target to the correct test location.This test was added in D74217 (and the `.categories` file later added in ccf1c30cde6e1e763e7c9cdd48a609a805166699) around the same time I moved the test tree from `lldb/packages/Python/lldbsuite/test` to `lldb/test/API` (D71151). Since this got lost in the move, it isn't running. (I introduced an intentional syntax error, and `ninja check-lldb` passes).I moved it to the correct location, and now it runs and passes -- locally, at least -- as `ninja check-lldb-api-tools-lldb-server-registers-target-xml-reading`.