gdbgui VS code-debug

how does it compare to https://github.com/cs01/gdbgui?

I was thinking about this project I tried a while ago.

We will use dap-mode with the dap-gdb-lldb option here. Under the hood, it uses the debug adapter from the Native Debug VSCode extension. Configuring it is described on the dap-mode webpages. After we have configured dap-mode, we could in theory reuse the launch.json configurations from the VSCode related articles above. That will require that you also use lsp-mode, as dap-launch depends on the lsp-workspace-root function and will not resolve when lsp-mode is not used. I don't use lsp-mode with C (company-clang and company-c-headers provide what I need), so the next logical solution would be to create a debug template ourselves:

I'm not sure.

I can see that this extension claims to make debugging with GDB work in VS Code:

https://github.com/WebFreak001/code-debug

and that at least for emacs there exists a project to use that extension:

https://github.com/emacs-lsp/dap-mode/blob/master/dap-gdb-ll...

Not having tried it, I can't speak to how well it works, and I don't know if there are adapters for other editors.

The link at the top of page here, references the github repo : https://github.com/WebFreak001/code-debug which isnt the same thing as installed by vscode or by running dap-gdb-lldb-setup . Indeed this link points to a codebase using .ts files in different locations to the VSCode extension installed .js files. (I did set up the dap program/path variables to use the .ts files but that didnt work)