en Copyright 2015 Java http://172.16.0.5:8080/history/llvm-project-15.0.7/lldb/test/API/tools/lldb-vscode/breakpoint-events/Makefile#878d82c4 Revert "[lldb-vscode] Emit the breakpoint changed event on location resolved"This reverts commit 1f21d488bd79a06c9cf405cc5db985fcd71c4f70. List of files: /llvm-project-15.0.7/lldb/test/API/tools/lldb-vscode/breakpoint-events/Makefile Sun, 21 Feb 2021 21:08:06 +0000 António Afonso <antonio.afonso@gmail.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/lldb/test/API/tools/lldb-vscode/breakpoint-events/Makefile#1f21d488 [lldb-vscode] Emit the breakpoint changed event on location resolvedVSCode was not being informed whenever a location had been resolved (after being initated as non-resolved), so even though it was actually resolved, the IDE would show a hollow dot (instead of a red dot) because it didn't know about the change.Differential Revision: https://reviews.llvm.org/D96680 List of files: /llvm-project-15.0.7/lldb/test/API/tools/lldb-vscode/breakpoint-events/Makefile Fri, 19 Feb 2021 17:43:38 +0000 António Afonso <antonio.afonso@gmail.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/lldb/test/API/tools/lldb-vscode/breakpoint-events/Makefile#9cb227f5 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: labathSubscribers: lldb-commitsTags: #lldbDifferential Revision: https://reviews.llvm.org/D73665 List of files: /llvm-project-15.0.7/lldb/test/API/tools/lldb-vscode/breakpoint-events/Makefile Wed, 29 Jan 2020 22:11:40 +0000 Greg Clayton <gclayton@fb.com>