csm101/delphi-visual-studio-code-debugger — explained in plain English
Analysis updated 2026-05-18
Debug Delphi Windows applications directly inside VS Code without needing the Delphi IDE.
Let an AI agent run your Delphi program, stop it at breakpoints, and read real variable values.
Attach a debugger to an already-running Delphi process to inspect its state and call stack.
Step through Delphi runtime packages and your own code with conditional breakpoints.
| csm101/delphi-visual-studio-code-debugger | tinybiggames/ganymede | vincitamore/pascal-gba | |
|---|---|---|---|
| Stars | 6 | 11 | 1 |
| Language | Pascal | Pascal | Pascal |
| Setup difficulty | moderate | moderate | hard |
| Complexity | 4/5 | 4/5 | 4/5 |
| Audience | developer | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
You must compile Delphi projects with specific debug settings turned on, and a companion IDE plugin is recommended to handle the hundreds of search paths in real projects.
This repository provides a debugger for Delphi Win64 applications that works outside of Embarcadero's own IDE. It is built on the Windows Debug API and written in Delphi. The project contains three programs that share one underlying debugger engine: a debug adapter that handles breakpoints and stepping, a VS Code extension that makes the debugger usable inside the editor, and an MCP server that exposes the same engine to an AI agent so it can run a program, stop it, and read its actual state. The shared engine lives in a folder called DebuggerCore. It contains the Windows Debug API loop, symbol readers for several formats, and an expression evaluator. The three front ends are thin layers on top of this core. The MCP server offers 33 tools, including setting breakpoints, stepping into code, reading local variables, evaluating expressions, and reading memory. This means an AI agent can inspect a running program's real state instead of guessing from source code. The README strongly recommends also installing a companion Delphi IDE plugin that generates workspace and launch configuration files for your projects. A real Delphi project can have hundreds of search paths, and the plugin handles that automatically. The debugger works without it if you write the configuration by hand, but the plugin makes it practical. A critical requirement is that you must compile the program you want to debug with full debug information. The README details which Delphi compiler settings to enable: turn off optimization, turn on debug information and local symbols, and include remote debug symbols. Without these, breakpoints will not work correctly and local variables will read as garbage. The same applies to runtime packages you want to step into. The project is described as working and feature-rich. It supports launch and attach modes, conditional and hit-count breakpoints, stepping in all directions, call stacks with function names, variable inspection with type-aware formatting, a full Pascal expression evaluator, and a configurable exception engine. For users who just want to try it, a prebuilt installer is available from the releases page with no build step required. The full README is longer than what was shown.
A debugger for Delphi Windows programs that works in VS Code or with AI agents, letting you set breakpoints, step through code, and inspect variables without the Delphi IDE.
Mainly Pascal. The stack also includes Delphi, Pascal, Windows Debug API.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
double-check against the repo, no cap.