37
submitted 1 year ago* (last edited 1 year ago) by ZILtoid1991@kbin.social to c/programming@programming.dev

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.

you are viewing a single comment's thread
view the rest of the comments
[-] pfech@lemmy.ml 3 points 1 year ago

It's not often talked about but WinDbg is a great tool: https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/

this post was submitted on 27 Aug 2023
37 points (100.0% liked)

Programming

17540 readers
46 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 2 years ago
MODERATORS