git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH V1 1/1] contrib/vscode/: debugging with VS Code and gdb

From
Matthieu Moy <matthieu.moy@univ-lyon1.fr>
Date
Apr 7, 2022, 08:59 UTC
Message-ID
<6a5152c1-7bb4-220c-cdce-33e93ea9c7c6@univ-lyon1.fr>
In-Reply-To
<66f08cb2e81647e29a080af05d7c867e@SAMBXP02.univ-lyon1.fr>
On 4/6/22 10:47, Ævar Arnfjörð Bjarmason wrote:
Show 8 quoted lines
> 
> On Wed, Apr 06 2022, COGONI Guillaume wrote:
> 
> I really don't mind having some guide for VSCode in our developer
> documentation, but I think if we (as a free software project) are
> recommending proprietary software we should put that in some context
> where we explain if/why it's needed, and if free alternatives are also
> suitable.

Note that VS Code is mostly open source (the pre-compiled binaries are proprietary, but the source code is MIT licenced, https://github.com/Microsoft/vscode). Not to be confused with Visual Studio, which is fully proprietary, but is a totally different tool (AFAIK, they only share the name).

> I haven't used the VSCode integration you're documenting, but from the
> diff and the "gdb" mention I gather that this isn't using some "native"
> debugger of MSVC/VS's, but just using the VSCode editor as a wrapper for
> gdb?

Yes (gdb or lldb under the hood). As usual, it adds a GUI layer, but also a configuration layer where you specify how to launch the debugger in a launch.json file, and this is where the little script in contrib/ is handy to generate a launch.json adapted for Git.

> If that's the case wouldn't it suffice to link to some generic getting
> started guide for debuggers? And e.g. recommend the GDB manual, maybe
> there's a better online reference (I read it locally), but e.g.:
> https://www.sourceware.org/gdb/current/onlinedocs/gdb.html

To me the point of the doc within Git's repo is to document git-specific aspects, and I agree that pointing to a generic doc is better than re-writing one. If I had written the patch I'd have made the general paragraph on debugger benefits a bit shorter, but it's already rather short so I'm OK with the patch in its current state.

> Then if we're recommending GUI wrappers those are a dime a dozen,
> e.g. Emacs's GUD mode:
> https://www.gnu.org/software/emacs/manual/html_node/emacs/Debuggers.html

To me this is out of the scope of the patch (the real point to me was to increase the discoverability of contrib/vscode), but sure, documenting other GUI wrappers would be nice.

-- 
Matthieu Moy
https://matthieu-moy.fr/
Previous: COGONI Guillaume
Message 24 of 24 in “contrib/vscode/: debugging with vscode and gdb”
  1. Jonathan BressatMar 24, 2022
  2. Derrick StoleeMar 25, 2022
  3. Matthieu MoyMar 25, 2022
  4. Derrick StoleeMar 25, 2022
  5. Jonathan BressatMar 26, 2022
  6. Guillaume CogoniApr 3, 2022
  7. Matthieu MoyApr 5, 2022
  8. 0/1 contrib/vscode/: debugging with VS Code and gdbCOGONI Guillaume, Apr 5, 2022
  9. 1/1 contrib/vscode/: debugging with VS Code and gdbCOGONI Guillaume, Apr 5, 2022
  10. Ævar Arnfjörð BjarmasonApr 6, 2022
  11. Matthieu MoyApr 6, 2022
  12. Matthieu MoyApr 6, 2022
  13. 0/1 contrib/vscode/: debugging with VS Code and gdbCOGONI Guillaume, Apr 6, 2022
  14. 1/1 contrib/vscode/: debugging with VS Code and gdbCOGONI Guillaume, Apr 6, 2022
  15. Derrick StoleeApr 6, 2022
  16. Junio C HamanoApr 6, 2022
  17. 0/1 contrib/vscode/: debugging with VS Code and gdbCOGONI Guillaume, Apr 6, 2022
  18. 1/1 contrib/vscode/: debugging with VS Code and gdbCOGONI Guillaume, Apr 6, 2022
  19. Ævar Arnfjörð BjarmasonApr 7, 2022
  20. Derrick StoleeApr 7, 2022
  21. Junio C HamanoApr 7, 2022
  22. 0/1 contrib/vscode/: debugging with VS Code and gdbCOGONI Guillaume, Apr 7, 2022
  23. 1/1 contrib/vscode/: debugging with VS Code and gdbCOGONI Guillaume, Apr 7, 2022
  24. Matthieu MoyApr 7, 2022

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.