Why does the box crash after VC2010 starts debugging? How can I not see the results of the operation

"Flashback" is actually closed directly after the execution is completed. If you press the "Debug" button (or F5) directly, that's it, normal.

Method: You can press CTRL+F5 to "execute", which can generally be solved.

If it hasn't been solved, it's okay to add ** lines on the Internet or ask you to set up subsystems, but I don't think it's perfect, and you still need to know the problem. In fact, when you start to build a project, you have to choose to create a "win32 console application", and then only check the "empty project" in the wizard, and the rest remains the same, so that the built project will be retained after compiling it, and then press the ctrl+f5 window just said. This is also a common problem encountered by novices.

I've also been bothered by this problem for a long time, can I only use fn+ctrl+f5 to solve the so-called "running flashback" problem? Later, I felt that debugging and running are different, that is to say, clicking on debugging can only check whether the program has errors, not running, and some people have said in this statement, so now there is a compromise method, that is, to find "run", this function is hidden deeply, and the following begins to find:

Step 1: Go to the menu bar (light blue box at the top of the VS2010 interface) and right-click in the blank space.

Step 2: At the very bottom of the pop-up window, click "Customize" with the left mouse button.

Step 3: Left-click on "Commands" in the "Customize" window.

Step 4: Find "Add Command" in the "Commands" page, left-click this "Add Command".

Step 5: In the "Category" column of the pop-up "Add Command" window, find "Debug" and left-click to enter.

Step 6: In the corresponding "Command" column on the right, find "Start Execution (without debugging)" and left-click.

Step 7: Left-click "OK" below to close the window.

Step 8: Left-click "Close" below to close the window.

Once you've done that, you'll notice a hollow triangle in the menu bar, which is the "run" you've been looking for.

When the VC debugging window flashes and disappears, it may be that the debugging window is closed or hidden. This could be due to a crash or an error in the program, causing the program to quit or terminate suddenly. It's also possible that the debug window is minimized or hidden behind other windows and can't be displayed.

In order to solve this problem, here are a few things you can try:

Check: The first thing you need to do is check the program for errors or exceptions. If there is a crash or error in the program, the debugging window may be closed or hidden.

Open the debugging window manually: You can try to open the debugging window manually, or use shortcut keys to open the debugging window, such as "Ctrl + Alt + I" to open the "Output" window. If the debugging window is hidden or minimized, you can try reverting it.

Adjust the debugging settings: You can try to adjust the debugging settings of the VC, for example, select "Options" in the "Tools" menu, then select "Debugging", and check "Debugger Output" and "Console Application Output" in the "Debug Output" options, so that the debugging information can be output to the console or debugging window, and Liquid Wisdom can easily view it.

Upgrade the VC version: If the problem cannot be resolved, you can consider upgrading the VC version or reinstalling the VC to ensure that the software is running properly.

In short, when the VC debugging window flashes and disappears, you need to check the program**, manually open the debugging window, adjust the debugging settings, or upgrade the VC version to solve the problem.