|
Revision tags: llvmorg-21-init, llvmorg-19.1.7, llvmorg-19.1.6 |
|
| #
ff595380 |
| 04-Dec-2024 |
Jonas Devlieghere <jonas@devlieghere.com> |
[lldb-dap] Support finding the lldb-dap binary (#118547)
Support finding the lldb-dap binary with `xcrun` on Darwin or in PATH on
all other platforms.
Unfortunately, this PR is larger than I wou
[lldb-dap] Support finding the lldb-dap binary (#118547)
Support finding the lldb-dap binary with `xcrun` on Darwin or in PATH on
all other platforms.
Unfortunately, this PR is larger than I would like because it removes
the `lldbDapOptions`. I believe these options are not necessary, and as
previously implemented, they caused a spurious warning with this change.
The problem was that the options were created before the custom factory.
By moving the creation logic into the factory, we make sure it's only
called after the factory has been registered. The upside is that this
simplifies the code and removes a level of indirection.
show more ...
|
|
Revision tags: llvmorg-19.1.5, llvmorg-19.1.4, llvmorg-19.1.3, llvmorg-19.1.2, llvmorg-19.1.1 |
|
| #
30eb1932 |
| 18-Sep-2024 |
Serban <serbyme-git@yahoo.com> |
[LLDB][lldb-dap][vscode-lldb] Add Environment configuration for the lldb-dap process (#108948)
Frequently, environment variables such as `LLDB_USE_NATIVE_PDB_READER`
are needed to be able to use ll
[LLDB][lldb-dap][vscode-lldb] Add Environment configuration for the lldb-dap process (#108948)
Frequently, environment variables such as `LLDB_USE_NATIVE_PDB_READER`
are needed to be able to use lldb-dap in vscode
This PR adds a way to set the environment for the lldb-dap process using
configuration.
show more ...
|
|
Revision tags: llvmorg-19.1.0, llvmorg-19.1.0-rc4 |
|
| #
984fca5a |
| 01-Sep-2024 |
Da-Viper <57949090+Da-Viper@users.noreply.github.com> |
[lldb-dap] show dialog when executable is not found (#104711)
|
|
Revision tags: llvmorg-19.1.0-rc3 |
|
| #
78988660 |
| 15-Aug-2024 |
Adrian Vogelsgesang <avogelsgesang@salesforce.com> |
[lldb-dap] Expose log path in extension settings (#103482)
lldb-dap already supports a log file which can be enabled by setting the
`LLDBDAP_LOG` environment variable. With this commit, the log loc
[lldb-dap] Expose log path in extension settings (#103482)
lldb-dap already supports a log file which can be enabled by setting the
`LLDBDAP_LOG` environment variable. With this commit, the log location
can be set directly through the VS-Code extension settings.
Also, this commit bumps the version number, such that the new VS Code
extension gets published to the Marketplace.
show more ...
|
|
Revision tags: llvmorg-19.1.0-rc2, llvmorg-19.1.0-rc1, llvmorg-20-init, llvmorg-18.1.8, llvmorg-18.1.7, llvmorg-18.1.6, llvmorg-18.1.5, llvmorg-18.1.4, llvmorg-18.1.3, llvmorg-18.1.2, llvmorg-18.1.1, llvmorg-18.1.0, llvmorg-18.1.0-rc4, llvmorg-18.1.0-rc3, llvmorg-18.1.0-rc2, llvmorg-18.1.0-rc1, llvmorg-19-init |
|
| #
b5d43322 |
| 09-Jan-2024 |
Walter Erquinigo <a20012251@gmail.com> |
[lldb-dap] Create a typescript extension for lldb-dap (#75515)
The main motivations behind this are two:
- Allow different companies developing their own vscode extensions for
LLDB to have a sin
[lldb-dap] Create a typescript extension for lldb-dap (#75515)
The main motivations behind this are two:
- Allow different companies developing their own vscode extensions for
LLDB to have a single contribution point, thus sharing resources and
working as a virtual large team.
- Allow for visual ways to configure the debugger, which currently has
to be done through launch.json files.
In terms of implementation, this is very straightforward and these are
the most important details:
- All the cpp code has been moved to a subfolder for cleanness. There's
a specific commit in the list of commits of this PR that just does that,
in case that helps reviewing this.
- A new folder `src-ts` has been created for the typescript code
- The ts extension can be used in two ways: as a regular vscode
extension and as a library. There file `extension.ts` explains which
entry point to use.
- The README has been updated the mention how to install the extension,
which is simpler than before. There are two additional sections for
rebuilding and formatting.
- The ts code I added merely sets up the debug adapter using two
possible options: reading the lldb-dap path from vscode settings or from
a config object passed by users of the extension is used as a library. I
did this to show how we can support easily both worlds.
show more ...
|