Skip to content
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

Unable to find GDB #143

Open
romangg opened this issue Sep 7, 2024 · 6 comments
Open

Unable to find GDB #143

romangg opened this issue Sep 7, 2024 · 6 comments
Assignees
Labels
bug Something isn't working

Comments

@romangg
Copy link
Contributor

romangg commented Sep 7, 2024

When following the guide debugging is not possible because it can't find GDB. Running works fine though.

Screenshot_20240907_170132

@romangg romangg added the bug Something isn't working label Sep 7, 2024
@romangg
Copy link
Contributor Author

romangg commented Sep 7, 2024

Maybe just needs to be installed to the container?

@LordTermor
Copy link
Collaborator

LordTermor commented Sep 7, 2024

It uses lldb.

I've updated needed vscode extension, now it uses official llvm-vs-code-extensions.lldb-dap instead of third party vadimcn.vscode-lldb and should try to run /bin/lldb-vscode-17, not lldb-mi.

Try to install the extension.

@romangg
Copy link
Contributor Author

romangg commented Sep 7, 2024

I'm pretty sure I installed all extensions it asked for. Let me try again.

@romangg
Copy link
Contributor Author

romangg commented Sep 8, 2024

The extension llvm-vs-code-extensions.lldb-dap is installed in the container. There is /bin/lldb-vscode-17 but no /bin/lldb-dab what the extension says would be needed.

@LordTermor
Copy link
Collaborator

They've renamed the executable in llvm 18, we're still 17.

Check launch.conf and settings of this extension, I've added needed path to the config but maybe it conflicts with something.

Actually, judging from your screenshot it looks like you're trying to debug using Microsoft's cpptools and not lldb-dap, how exactly are you running the debugger?

@romangg
Copy link
Contributor Author

romangg commented Sep 8, 2024

Like that:
Screenshot_20240908_110234

This is run form a complete new local checkout of the project. So it should work out-of-the-box without any manual changes necessary. I installed all recommended extensions in the dev container too.

Now that you mention it though, going to the "Run and Debug" screen and pressing there on Start Debugging works though. Doing that once adds another button to the bottom:

Screenshot_20240908_110830

It would be nice if the "Launch the debugger for the selected target" button is doing something useful too and not error out what is confusing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants