Changes in ExceptionBreakpoint.cpp

b99d4112585302cbd01f9b851a04adc6e4fb5218 - [lldb-dap] Refactoring breakpoints to not use the `g_dap` reference. (#115208)

Fri, 08 Nov 2024 21:36:25 +0000

[lldb-dap] Refactoring breakpoints to not use the `g_dap` reference. (#115208)Refactoring breakpoints to not use the `g_dap` reference. Instead, when a breakpoint is constructed it will be passed a DAP reference that it should use for its lifetime. This is part of a larger refactor to remove the global `g_dap` variable to allow us to create multiple DAP instances. --------- Co-authored-by: Pavel Labath List of files: /llvm-project/lldb/tools/lldb-vscode/ExceptionBreakpoint.cpp

01263c6c6fb495a94fe0ccbb1420bb1ec8460748 - [lldb] Rename lldb-vscode to lldb-dap (#69264)

Thu, 19 Oct 2023 16:48:54 +0000

[lldb] Rename lldb-vscode to lldb-dap (#69264)Rename lldb-vscode to lldb-dap. This change is largely mechanical. The following substitutions cover the majority of the changes in this commit: s/VSCODE/DAP/ s/VSCode/DAP/ s/vscode/dap/ s/g_vsc/g_dap/ Discourse RFC: https://discourse.llvm.org/t/rfc-rename-lldb-vscode-to-lldb-dap/74075/ List of files: /llvm-project/lldb/tools/lldb-vscode/ExceptionBreakpoint.cpp

9cb227f561f4e5491840694580abbe7c0123b358 - Stop emitting a breakpoint for each location in a breakpoint when responding to breakpoint commands.

Wed, 29 Jan 2020 22:11:40 +0000

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/lldb/tools/lldb-vscode/ExceptionBreakpoint.cpp

2946cd701067404b99c39fb29dc9c74bd7193eb3 - Update the file headers across all of the LLVM projects in the monorepo

Sat, 19 Jan 2019 08:50:56 +0000

Update the file headers across all of the LLVM projects in the monorepoto reflect the new license.We understand that people may be surprised that we're moving the headerentirely to discuss the new license. We checked this carefully with theFoundation's lawyer and we believe this is the correct approach.Essentially, all code in the project is now made available by the LLVMproject under our new license, so you will see that the license headersinclude that license only. Some of our contributors have contributedcode under our old license, and accordingly, we have retained a copy ofour old license notice in the top-level files in each project andrepository.llvm-svn: 351636 List of files: /llvm-project/lldb/tools/lldb-vscode/ExceptionBreakpoint.cpp

2f5cf8511a3f0ad97db2acf51c6c9ea0ddc9da92 - Add a new tool named "lldb-vscode" that implements the Visual Studio Code Debug Adaptor Protocol

Thu, 16 Aug 2018 17:59:38 +0000

Add a new tool named "lldb-vscode" that implements the Visual Studio Code Debug Adaptor ProtocolThis patch adds a new lldb-vscode tool that speaks the Microsoft Visual Studio Code debug adaptor protocol. It has full unit tests that test all packets.This tool can be easily packaged up into a native extension and used with Visual Studio Code, and it can also be used by NuclideDifferential Revision: https://reviews.llvm.org/D50365llvm-svn: 339911 List of files: /llvm-project/lldb/tools/lldb-vscode/ExceptionBreakpoint.cpp