Basic / minimal / working configuration for C++ and lldb-vscode-11? #158
Replies: 2 comments 6 replies
-
Could be both. Other than that you can try to increase the log level (See
For the arguments to your app that you want to debug? You can change the |
Beta Was this translation helpful? Give feedback.
-
I found this question because I also am confused by the configurations for lldb. I can get the debugger launched, but I have no terminal where I can write to stdin. stdout comes out on the repl. local dap = require'dap'
dap.adapters.cpp = {
type = 'executable',
command = 'lldb-vscode',
env = {
LLDB_LAUNCH_FLAG_LAUNCH_IN_TTY = "YES"
},
name = "lldb"
}
dap.configurations.cpp = {
{
name = "Launch",
type = "cpp",
request = "launch",
program = function()
return vim.fn.input('Path to executable: ', vim.fn.getcwd() .. '/', 'file')
end,
cwd = '${workspaceFolder}',
args = {}
}
}
dap.configurations.c = dap.configurations.cpp
|
Beta Was this translation helpful? Give feedback.
-
Thank you for the nice plugin, I have tried to set it up but I can't get it to work.
Scrounging from the Internet and this forum, I came up with this configuration:
I press "continue" and I get prompted for the binary name. Then after a pause of several seconds I get "Client 1 quit with exit code 0 and signal 6". Not sure if my program or lldb-vscode sent sigabrt. I am using lldb-vscode-11 packaged by Debian and I don't have a VSCode installation to test it with.
What am I missing?
Also, what is a magic lua incantation to get NVIM to prompt me for the arguments?
Thanks again,
florin
Beta Was this translation helpful? Give feedback.
All reactions