5 Commits

Author	SHA1	Message	Date
Walter Erquinigo	8e40987e18	Fix e796c77b26 ... Failure: http://green.lab.llvm.org/green/view/LLDB/job/lldb-cmake/14556/testReport/junit/lldb-api/tools_lldb-vscode_breakpoint-events/TestVSCode_breakpointEvents_py/ Diff: [lldb-vscode] Correctly return source mapped breakpoints for setBreakpoints request https://reviews.llvm.org/D76968 It failed a test TestVSCode_breakpointEvents that only runs Darwin that needed to be updated to match the current logic. The change is simple.	2020-04-08 10:48:01 -07:00
Kazuaki Ishizaki	e9264b746b	[lldb] NFC: Fix trivial typo in comments, documents, and messages ... Differential Revision: https://reviews.llvm.org/D77460	2020-04-07 01:06:16 +09:00
Pavel Labath	189c701332	[lldb] Remove accidentally checked-in debugging code	2020-02-14 10:21:35 +01:00
Greg Clayton	c84a0bd9ad	Fix buildbots by disabling this new test until I can fix it. ... This tests works on Darwin. I will need to check windows and linux.	2020-02-13 09:32:19 -08:00
Greg Clayton	9cb227f561	Stop emitting a breakpoint for each location in a breakpoint when responding to breakpoint commands. ... Summary: The VS Code DAP expects on response for each breakpoint that was requested. If we responsd with multiple entries for one breakpoint the VS Code UI gets out of date. Currently the VS code DAP doesn't handle one breakpoint with multiple locations. If this ever gets fixed we can modify our code. Reviewers: labath Subscribers: lldb-commits Tags: #lldb Differential Revision: https://reviews.llvm.org/D73665	2020-02-13 08:23:19 -08:00