c++ - What are the advantages of VS2014 in debugging compared to codeblocks, devcpp and other software?

Question

I just uninstalled vs. It feels too big and takes up too much memory. I usually only type C algorithm questions with black windows, and I feel that using codeblocks is enough. Later, I heard someone say that the debugging function of VS is powerful. I want to know where the power is?

Answer 1

vs 2014?

Answer 2

I haven’t used the others much, so let’s talk about some experiences of vs debugging C++:
1. High degree of visualization. During the debugging process, you can intuitively query the variable values ​​of the current context (mouse value), tracking variable values ​​(Watch), call stack, parallel stack, memory block data (Memory), etc. at any time. Now the new version of VS supports DataTips, and you can expand the way the VS debugger displays variable values ​​​​by yourself.
2. Powerful breakpoint function. VS's breakpoint supports Conditions and Actions, which is convenient and easy to use.
3. Powerful exception capture capability. It is estimated that other IDEs also support it. . .
3. Attach to the process. As long as there is code or pdb file, you can debug the running program.
4, remote debugging. The remote debugging function of Windows Remote Debugger is very easy to use and is especially suitable for solving special bugs in production environments.
5, dump file debugging. Open the dump file directly for debugging.

VS’s debugging support for C++ and .net programs is really in place. It’s comfortable and natural to use, and various methods can basically solve various problems encountered. However, there are also areas that I feel are regrettable and should be strengthened:
1. Log output. At present, the log output (Output window) of VS is just a text outputter, which is relatively low-level compared to Eclipse. It does not support levels, does not support color, does not support filtering, does not support automatic formatting, does not support export, and does not support interaction. . .
2. Memory leak detection tool. VS does not come with a memory leak detection tool, and memory allocation and release tracking is beyond the control of novices. Think about xcode Instruments' NSZombieEnabled, and I feel envious and jealous.
3. Windbg is not integrated. The debugging commands of windbg are extremely powerful. It is a pity that VS does not integrate such an interactive window for debugging commands.