After a software update, VS2022 stopped working correctly. When I hit a break point, I don’t get any local variables and their values, instead I get a “wait…” label that looks like a button, and also VS is growing in memory size until it crashes my Windows, or I either stop the debugging or VS itself.
So far I get the best results by using x64dbg, but it has it’s own issues, namely that almost all guides only discuss its reverse engineering capabilities, and I need a development tool, so I don’t have to rely on printing to the console as debugging, which has a lot of issues (leaving in the print commands, etc). I’m programming in D, but it should work with any other debugger made for C, and up until recently I used VS for that purpose.
I would try to fix VS, uninstall it, check logs for errors, maybe ask support?
A simple downgrade solved the issue, but regardless of that I’ll try to look into some alternatives, especially since VS has licensing issues, which is fine for me as I use it for open source projects, but might not be fine for others who would use it for closed source projects, and I made my open source engine in a way it allows for be used in closed source projects.
Try deleting all obj and bin folders in the repo and restart VS. Sometimes it gets stuck on an old project reference and can’t clear out the cached files
Honestly it sounds like there’s an infinite loop in your code before it hits your breakpoint.
Remedybg ! Its paid but definitely worth it!
It’s not often talked about but WinDbg is a great tool: https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/
LLDB?
I’m unsure whether it’ll work for D, but remedyDB is the best debugger I’ve ever used personally
This is an admitted wild shot, but if you’re using D, you could try using GDB for Windows. It’s pretty simplified.
