projects / platform / upstream / llvm.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: e0615bc) | patch
[lldb-vscode] Emit the breakpoint changed event on location resolved
authorAntónio Afonso <antonio.afonso@gmail.com>
Fri, 19 Feb 2021 17:43:38 +0000 (09:43 -0800)
committerAntónio Afonso <antonio.afonso@gmail.com>
Sun, 21 Feb 2021 17:46:29 +0000 (09:46 -0800)
commit1f21d488bd79a06c9cf405cc5db985fcd71c4f70
tree938fe68585c027c0e4d430d0cdf50b283d15838atree | snapshot
parente0615bcd39fd863361ce8eb68aafdfcdcd8b067dcommit | diff
[lldb-vscode] Emit the breakpoint changed event on location resolved

VSCode 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
lldb/test/API/tools/lldb-vscode/breakpoint-events/Makefile diff | blob | history
lldb/test/API/tools/lldb-vscode/breakpoint-events/TestVSCode_breakpointLocationResolvedEvent.py [new file with mode: 0644] blob
lldb/test/API/tools/lldb-vscode/breakpoint-events/dylib.c [new file with mode: 0644] blob
lldb/test/API/tools/lldb-vscode/breakpoint-events/dylib_loader.c [new file with mode: 0644] blob
lldb/tools/lldb-vscode/lldb-vscode.cpp diff | blob | history
Domain: System / Toolchain;