en Copyright 2015 Java http://src.rcs.uwaterloo.ca:8080/source/history/llvm-project/lldb/test/API/tools/lldb-dap/databreakpoint/TestDAP_setDataBreakpoints.py#fa6377119c0624773cb698935692d46843e9f6ec [lldb-dap] Automatically skip lldb-dap tests for remote platforms (#93169)The don't currently work (and they're also not particularly useful, since all of the remote stuff happens inside lldb). This saves us from annotating tests one by one. List of files: /llvm-project/lldb/test/API/tools/lldb-dap/databreakpoint/TestDAP_setDataBreakpoints.py Fri, 24 May 2024 06:52:32 +0000 Pavel Labath <pavel@labath.sk> http://src.rcs.uwaterloo.ca:8080/source/history/llvm-project/lldb/test/API/tools/lldb-dap/databreakpoint/TestDAP_setDataBreakpoints.py#a4ad05284e97dd188c44252846486cbfb74a884c [lldb-dap] Replace `assertEquals` with `assertEqual` (NFC)Fixes new test that were added or modified after #82073. Also fixes aformatting issue. List of files: /llvm-project/lldb/test/API/tools/lldb-dap/databreakpoint/TestDAP_setDataBreakpoints.py Fri, 17 May 2024 17:11:29 +0000 Jonas Devlieghere <jonas@devlieghere.com> http://src.rcs.uwaterloo.ca:8080/source/history/llvm-project/lldb/test/API/tools/lldb-dap/databreakpoint/TestDAP_setDataBreakpoints.py#2cacc7a61095577ff42177373d46c8cb8df0cb1f [lldb-dap] Deduplicate watchpoints starting at the same address on SetDataBreakpointsRequest. (#83192)If a SetDataBreakpointsRequest contains a list data breakpoints which have duplicate starting addresses, the current behaviour is returning `{verified: true}` to both watchpoints with duplicated starting addresses. This confuses the client and what actually happens in lldb is the second one overwrite the first one. This fixes it by letting the last watchpoint at given address have `{verified: true}` and all previous watchpoints at the same address should have `{verfied: false}` at response. List of files: /llvm-project/lldb/test/API/tools/lldb-dap/databreakpoint/TestDAP_setDataBreakpoints.py Wed, 28 Feb 2024 19:56:55 +0000 Zequan Wu <zequanwu@google.com> http://src.rcs.uwaterloo.ca:8080/source/history/llvm-project/lldb/test/API/tools/lldb-dap/databreakpoint/TestDAP_setDataBreakpoints.py#df6f756a19277d936ec83f7cebc2501327ac3add Re-land [lldb-dap] Add support for data breakpoint. (#81909)This implements functionality to handle DataBreakpointInfo request and SetDataBreakpoints request. Previous commit https://github.com/llvm/llvm-project/commit/8c56e78ec531f0e2460213c20fff869b6b7add99 was reverted because setting 1 byte watchpoint failed in the new test on ARM64. So, I changed the test to setting 4 byte watchpoint instead, and hope this won't break it again. It also adds the fixes from https://github.com/llvm/llvm-project/pull/81680. List of files: /llvm-project/lldb/test/API/tools/lldb-dap/databreakpoint/TestDAP_setDataBreakpoints.py Thu, 22 Feb 2024 21:11:40 +0000 Zequan Wu <zequanwu@google.com> http://src.rcs.uwaterloo.ca:8080/source/history/llvm-project/lldb/test/API/tools/lldb-dap/databreakpoint/TestDAP_setDataBreakpoints.py#8c56e78ec531f0e2460213c20fff869b6b7add99 [lldb-dap] Add support for data breakpoint. (#81541)This implements functionality to handle `DataBreakpointInfo` request and `SetDataBreakpoints` request. If variablesReference is 0 or not provided, interpret name as ${number of bytes}@${expression} to set data breakpoint at the given expression because the spec https://microsoft.github.io/debug-adapter-protocol/specification#Requests_DataBreakpointInfo doesn't say how the client could specify the number of bytes to watch. This is based on top of https://github.com/llvm/llvm-project/pull/80753. List of files: /llvm-project/lldb/test/API/tools/lldb-dap/databreakpoint/TestDAP_setDataBreakpoints.py Tue, 13 Feb 2024 21:38:56 +0000 Zequan Wu <zequanwu@google.com>