I use a bit weird development setup. Since VisualD, the official plugin for VS adding D language support, does not have dub support (which D’s official package manager, and without it a lot of things get very hard to do, like dependency management), I have to use VSCode as my main code editor, build my code in command line, then load it in an empty VS project set up for C++ development.

However, since the latest update, VS2022 broke completely. I previously had issues with the option to break on every D exceptions disappearing, now I don’t even have that. When it hits a breakpoint or an exception, the debugger does not show the local variables, instead it has a “wait…” sign that looks like a button (but is unclickable), and the executable of VS grows until either crashes my Windows, or I stop either the debugging or VS. Probably would still work if I used it normally, but then I have to stop using dub as a build tool, and manage dependencies manually, which is a nightmare with bigger projects and dependencies having their own dependencies.

Currently I have some luck with x64dbg, but so far it’s not the most ideal solution. Almost all tutorials for it is about reverse engineering software without any available source code, and I need it as a development tool instead. It seems to load my symbol file and show call stack, but not local variables or source code. D should be able to work with most debuggers developed for C.