Skip to content

Debug use vscode lldb-dap extension #18257

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
kouhe3 opened this issue Oct 7, 2024 · 3 comments
Closed

Debug use vscode lldb-dap extension #18257

kouhe3 opened this issue Oct 7, 2024 · 3 comments
Labels
C-feature Category: feature request

Comments

@kouhe3
Copy link
Contributor

kouhe3 commented Oct 7, 2024

Now we have another lldb debug extension
https://marketplace.visualstudio.com/items?itemName=llvm-vs-code-extensions.lldb-dap

Can we add this?

Just out of curiosity, this looks the same as codelldb

@kouhe3 kouhe3 added the C-feature Category: feature request label Oct 7, 2024
@kouhe3
Copy link
Contributor Author

kouhe3 commented Oct 7, 2024

Well, Just to add, I prefer this official lldb-dap extension, which uses path's lldb instead of packaging lldb.exe and Python39.dll in vsix (Codelldb do this), it's smaller and Cross-platform

@lnicola
Copy link
Member

lnicola commented Oct 7, 2024

Sounds good, do you want to file a PR? See

const knownEngines: {
and
const commandCCpp: string = createCommandLink("ms-vscode.cpptools");
.

@kouhe3
Copy link
Contributor Author

kouhe3 commented Oct 7, 2024

I am writing, now can use lldb-dap + rust analyzer. But there are still some tasks todo.
lldb-dap requires arrays for env and sourcemap, instead of dict.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-feature Category: feature request
Projects
None yet
Development

No branches or pull requests

2 participants