Thread overview
Visual Studio 2022 no longer debugs D program, need an alternative debugger for Windows
Aug 26, 2023
solidstate1991
Aug 26, 2023
jmh530
Aug 26, 2023
solidstate1991
Aug 27, 2023
evilrat666
August 26, 2023

After a recent update, Visual Studio 2022 started to have serious troubles with D, namely having troubles with displaying debug variables, and growing constantly in memory until you either stop debugging or crashes Windows.

Currently I'm resorting to use x64dbg, which is currently the best I can use, and I'll try to look up some info on using it not as a reverse engineer tool, but as an actual debugger.

August 26, 2023

On Saturday, 26 August 2023 at 16:57:42 UTC, solidstate1991 wrote:

>

After a recent update, Visual Studio 2022 started to have serious troubles with D, namely having troubles with displaying debug variables, and growing constantly in memory until you either stop debugging or crashes Windows.

Currently I'm resorting to use x64dbg, which is currently the best I can use, and I'll try to look up some info on using it not as a reverse engineer tool, but as an actual debugger.

You should report this to bugzilla.

August 26, 2023

On Saturday, 26 August 2023 at 17:57:22 UTC, jmh530 wrote:

>

You should report this to bugzilla.

I'm using it in an unusual way. Since VisualD does not support dub, I have to rely on VSCode as my main editor, then load the executable in an empty C++ project in VS. This worked so far.

On the other hand, I'm having some good results with x64dbg, except I don't know how can I get locals to be displayed (which is the x64dbg is capable of, except all tutorials for it is about reverse engineering).

August 27, 2023
On 27/08/2023 6:47 AM, solidstate1991 wrote:
> On Saturday, 26 August 2023 at 17:57:22 UTC, jmh530 wrote:
>> You should report this to bugzilla.
> 
> I'm using it in an unusual way. Since VisualD does not support dub, I have to rely on VSCode as my main editor, then load the executable in an empty C++ project in VS. This worked so far.
> 
> On the other hand, I'm having some good results with x64dbg, except I don't know how can I get locals to be displayed (which is the x64dbg is capable of, except all tutorials for it is about reverse engineering).

Not unusual. However I attributed the breakage to -betterC + DLL's. Which clearly isn't the issue.
August 27, 2023

On Saturday, 26 August 2023 at 18:47:44 UTC, solidstate1991 wrote:

>

On Saturday, 26 August 2023 at 17:57:22 UTC, jmh530 wrote:

>

You should report this to bugzilla.

I'm using it in an unusual way. Since VisualD does not support dub, I have to rely on VSCode as my main editor, then load the executable in an empty C++ project in VS. This worked so far.

On the other hand, I'm having some good results with x64dbg, except I don't know how can I get locals to be displayed (which is the x64dbg is capable of, except all tutorials for it is about reverse engineering).

IIRC you can just drop(or open) the exe file directly on top of empty visual studio window and it is ready to debug.

Also VisualD with a dub project is not a problem, dub can generate VisualD project for you - "dub generate visuald"
("dub generate <:somesubpackage> visuald <other dub build options such as -ax64>")