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

Re: Using Visual Studio Code to Debug/Trace Git?

From
Jon Forrest <nobozo@gmail.com>
Date
Feb 12, 2025, 18:32 UTC
Message-ID
<09049b05-ed3f-4673-9d10-34870a70e2b3@gmail.com>
In-Reply-To
<Z4TJIzVc4Ib2QyPV@pks.im>

Just to follow up on this, I've had surprising success by simply building git the normal way (e.g. make), having VSCode open the directory contain the Git source code, opening common-main.c, and then executing "Start Debugging". I'm able to do full source-level debugging this way.

I'm not entirely sure why this works but it's good enough for me.

I'll be interested in seeing if the new Meson build system works any better in VSCode.

Cordially, Jon Forrest

Previous: Jon Forrest
Message 5 of 5 in “Using Visual Studio Code to Debug/Trace Git?”
  1. Jon ForrestJan 10, 2025
  2. Ben KnobleJan 10, 2025
  3. Patrick SteinhardtJan 13, 2025
  4. Jon ForrestJan 13, 2025
  5. Jon ForrestFeb 12, 2025

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.