[lldb] [test] Add a minimal test for x86 dbreg readingAdd a test verifying that after the 'watchpoint' command, new valuesof x86 debug registers can be read back correctly. The primary purposeof
[lldb] [test] Add a minimal test for x86 dbreg readingAdd a test verifying that after the 'watchpoint' command, new valuesof x86 debug registers can be read back correctly. The primary purposeof this test is to catch broken DRn reading and help debugging it.Differential Revision: https://reviews.llvm.org/D91264
show more ...
[lldb] [test/Register] Use initial state for write testsReset registers to their 'initial' state instead of a semi-randompattern in write tests. While the latter might have been helpfulwhile deb
[lldb] [test/Register] Use initial state for write testsReset registers to their 'initial' state instead of a semi-randompattern in write tests. While the latter might have been helpfulwhile debugging failures (i.e. to distinguish unmodified registersfrom mistakenly written zeroes), the former makes it possible to testwhether xstate_bv field is written correctly when using XSAVE.With this change, the four relevant tests start failing on NetBSDwithout D90105.Differential Revision: https://reviews.llvm.org/D90114
[lldb] [test/Register] Add read/write tests for multithreaded processAdd a test to verify that 'register read' and 'register write' commandswork correctly in a multithreaded program, in particular
[lldb] [test/Register] Add read/write tests for multithreaded processAdd a test to verify that 'register read' and 'register write' commandswork correctly in a multithreaded program, in particular that they reador write registers for the correct thread. The tests use lockingto ensure that events are serialized and the test can execute reliably.Differential Revision: https://reviews.llvm.org/D89248
[lldb] [test/Register] Attempt to fix x86-fp-read.test on DarwinDarwin seems to use stmmN instead of stN. Use a regex to accept both.Also try to actually clear st(7).Differential revision: http
[lldb] [test/Register] Attempt to fix x86-fp-read.test on DarwinDarwin seems to use stmmN instead of stN. Use a regex to accept both.Also try to actually clear st(7).Differential revision: https://reviews.llvm.org/D88795
[lldb] [test/Register] Add read/write tests for x87 regsAdd a partial read/write tests for x87 FPU registers. This includesreading and writing ST registers, control registers and floating-pointe
[lldb] [test/Register] Add read/write tests for x87 regsAdd a partial read/write tests for x87 FPU registers. This includesreading and writing ST registers, control registers and floating-pointexception data registers (fop, fip, fdp).The tests assume the current (roughly incorrect) behavior of reportingthe 'abridged' 8-bit ftag state as 16-bit ftag. They also assume Linuxplugin behavior of reporting fip/fdp split into halves as (fiseg, fioff)and (foseg, fooff).Differential Revision: https://reviews.llvm.org/D88583
[LLDB] [Windows] Initial support for ARM register contextsDifferential Revision: https://reviews.llvm.org/D69226llvm-svn: 375392
[LLDB] [Windows] Initial support for ARM64 register contextsDifferential Revision: https://reviews.llvm.org/D67954llvm-svn: 374866
Re-land "[test] Split LLDB tests into API, Shell & Unit"The original patch got reverted because it broke `check-lldb` on a cleanbuild. This fixes that.llvm-svn: 374201
Revert [test] Split LLDB tests into API, Shell & Unitas it appears to have broken check-lldb.This reverts r374184 (git commit 22314179f0660c172514b397060fd8f34b586e82)llvm-svn: 374187
[test] Split LLDB tests into API, Shell & UnitLLDB has three major testing strategies: unit tests, tests that exercisethe SB API though dotest.py and what we currently call lit tests. Thelater is
[test] Split LLDB tests into API, Shell & UnitLLDB has three major testing strategies: unit tests, tests that exercisethe SB API though dotest.py and what we currently call lit tests. Thelater is rather confusing as we're now using lit as the driver for allthree types of tests. As most of this grew organically, the directorystructure in the LLDB repository doesn't really make this clear.The 'lit' tests are part of the root and among these tests there's aUnit and Suite folder for the unit and dotest-tests. This layout makesit impossible to run just the lit tests.This patch changes the directory layout to match the 3 testingstrategies, each with their own directory and their own configurationfile. This means there are now 3 directories under lit with 3corresponding targets: - API (check-lldb-api): Test exercising the SB API. - Shell (check-lldb-shell): Test exercising command line utilities. - Unit (check-lldb-unit): Unit tests.Finally, there's still the `check-lldb` target that runs all three testsuites.Finally, this also renames the lit folder to `test` to match the LLVMrepository layout.Differential revision: https://reviews.llvm.org/D68606llvm-svn: 374184