• solidstate1991 (7/7) Aug 26 2023 After a recent update, Visual Studio 2022 started to have serious
• jmh530 (2/9) Aug 26 2023 You should report this to bugzilla.
• solidstate1991 (8/9) Aug 26 2023 I'm using it in an unusual way. Since VisualD does not support
• Richard (Rikki) Andrew Cattermole (3/13) Aug 26 2023 Not unusual. However I attributed the breakage to -betterC + DLL's.
• evilrat666 (7/16) Aug 27 2023 IIRC you can just drop(or open) the exe file directly on top of

solidstate1991 <laszloszeremi outlook.com> writes:

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.

jmh530 <john.michael.hall gmail.com> writes:

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.

solidstate1991 <laszloszeremi outlook.com> writes:

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).

"Richard (Rikki) Andrew Cattermole" <richard cattermole.co.nz> writes:

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.

evilrat666 <evilrat666 gmail.com> writes:

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>")