the compiled executable along with the debugging information (PDB files).I have already praised windbg for post mortem debugging using crash minidumps so I am delighted to find yet another use for this miniature tool.ĭebugging without visual studio requires: that's a lot of virtual machines!Īfter automatic windows updates gobbled up the allocated space in a few of the virtual machines I set up rather sparringly, I realized that I could uninstall visual studio and have almost the same debugging capabilities using a single 500KB (!) program windbg, the "user friendly" windows debugger. I test on windows 98, 2000, XP, vista, windows 7, 8, 8.1 and don't forget that most versions have a separate 32 and 64 bit flavor. Having one copy of visual studio installed is bad enough, but what if you had to have 10 copies? Nowadays, one needs to test code in a variety of operating systems, which means multiple virtual machines, each one of which needs a separate copy of the same programs and tools. ![]() Version 6 that I mostly use is 175MB installed, whereas VS2010 breaks the scales at 1.57GB, a 10-fold increase of lard without much benefit It is a splendid tool but over the years got extremely bloated. ![]() Most windows developers spend their life using Microsoft Visual Studio, an integrated development environment (IDE) that edits and debugs C++ programs and other languages. ![]() ■ Full-featured debugging with minimal toolset: windbg
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |