Закрывается консоль при ошибке visual studio

asked Nov 21, 2009 at 15:58

answered Nov 21, 2009 at 16:00

Right click on your project

Properties > Configuration Properties > Linker > System

Select Console (/SUBSYSTEM:CONSOLE) in SubSystem option or you can just type Console in the text field!

Now try it…it should work

Starting from Visual Studio 2017 (15.9.4) there is an option:

Tools->Options->Debugging->Automatically close the console

The corresponding fragment from the Visual Studio documentation:

Automatically close the console when debugging stops:

Tells Visual Studio to close the console at the end of a debugging session.

Here is a way for C/C++:

#include <stdlib.h>

#ifdef _WIN32
    #define WINPAUSE system("pause")
#endif

Put this at the top of your program, and IF it is on a Windows system (#ifdef _WIN32), then it will create a macro called WINPAUSE. Whenever you want your program to pause, call WINPAUSE; and it will pause the program, using the DOS command. For other systems like Unix/Linux, the console should not quit on program exit anyway.

answered Sep 28, 2012 at 9:24

If you’re using .NET, put Console.ReadLine() before the end of the program.

It will wait for <ENTER>.

answered Nov 21, 2009 at 16:00

(/SUBSYSTEM:CONSOLE) did not worked for my vs2013 (I already had it).

«run without debugging» is not an options, since I do not want to switch between debugging and seeing output.

I ended with

int main() {
  ...
#if _DEBUG
  LOG_INFO("end, press key to close");
  getchar();
#endif // _DEBUG
  return 0;
}

Solution used in qtcreator pre 2.6. Now while qt is growing, vs is going other way. As I remember, in vs2008 we did not need such tricks.

answered Oct 15, 2014 at 14:35

just put as your last line of code:

system("pause");

answered Jan 9, 2018 at 22:59

Here’s a solution that (1) doesn’t require any code changes or breakpoints, and (2) pauses after program termination so that you can see everything that was printed. It will pause after either F5 or Ctrl+F5. The major downside is that on VS2013 Express (as tested), it doesn’t load symbols, so debugging is very restricted.

1. Create a batch file. I called mine runthenpause.bat, with the following contents:

   %1 %2 %3 %4 %5 %6 %7 %8 %9
   pause
   

   The first line will run whatever command you provide and up to eight arguments. The second line will… pause.

2. Open the project properties | Configuration properties | Debugging.

3. Change «Command Arguments» to $(TargetPath) (or whatever is in «Command»).
4. Change «Command» to the full path to runthenpause.bat.
5. Hit OK.

Now, when you run, runthenpause.bat will launch your application, and after your application has terminated, will pause for you to see the console output.

I will post an update if I figure out how to get the symbols loaded. I tried /Z7 per this but without success.

answered Nov 28, 2009 at 20:13

GeoGeo

91.8k115 gold badges343 silver badges516 bronze badges

Just press CNTRL + F5 to open it in an external command line window (Visual Studio does not have control over it).

If this doesn’t work then add the following to the end of your code:

Console.WriteLine("Press any key to exit...");
Console.ReadKey();

This wait for you to press a key to close the terminal window once the code has reached the end.

If you want to do this in multiple places, put the above code in a method (e.g. private void Pause()) and call Pause() whenever a program reaches a possible end.

answered Jan 30, 2015 at 19:48

A somewhat better solution:

atexit([] { system("PAUSE"); });

at the beginning of your program.

Pros:

• can use std::exit()
• can have multiple returns from main
• you can run your program under the debugger
• IDE independent (+ OS independent if you use the cin.sync(); cin.ignore(); trick instead of system("pause");)

Cons:

• have to modify code
• won’t pause on std::terminate()
• will still happen in your program outside of the IDE/debugger session; you can prevent this under Windows using:

extern "C" int __stdcall IsDebuggerPresent(void);
int main(int argc, char** argv) {
    if (IsDebuggerPresent())
        atexit([] {system("PAUSE"); });
    ...
}

answered Oct 23, 2017 at 20:37

AAEMAAEM

1,8272 gold badges17 silver badges26 bronze badges

0xsteve0xsteve

1011 silver badge4 bronze badges

user1323995user1323995

1,1761 gold badge9 silver badges16 bronze badges

JuanJuan

15.1k23 gold badges99 silver badges184 bronze badges

KANJICODERKANJICODER

3,47729 silver badges16 bronze badges

GáborGábor

9,0873 gold badges59 silver badges77 bronze badges

Go to Setting>Debug>Un-check close on end.

answered Jun 27, 2020 at 16:32

asked Nov 21, 2009 at 15:58

answered Nov 21, 2009 at 16:00

Right click on your project

Properties > Configuration Properties > Linker > System

Select Console (/SUBSYSTEM:CONSOLE) in SubSystem option or you can just type Console in the text field!

Now try it…it should work

Starting from Visual Studio 2017 (15.9.4) there is an option:

Tools->Options->Debugging->Automatically close the console

The corresponding fragment from the Visual Studio documentation:

Automatically close the console when debugging stops:

Tells Visual Studio to close the console at the end of a debugging session.

Here is a way for C/C++:

#include <stdlib.h>

#ifdef _WIN32
    #define WINPAUSE system("pause")
#endif

Put this at the top of your program, and IF it is on a Windows system (#ifdef _WIN32), then it will create a macro called WINPAUSE. Whenever you want your program to pause, call WINPAUSE; and it will pause the program, using the DOS command. For other systems like Unix/Linux, the console should not quit on program exit anyway.

answered Sep 28, 2012 at 9:24

If you’re using .NET, put Console.ReadLine() before the end of the program.

It will wait for <ENTER>.

answered Nov 21, 2009 at 16:00

(/SUBSYSTEM:CONSOLE) did not worked for my vs2013 (I already had it).

«run without debugging» is not an options, since I do not want to switch between debugging and seeing output.

I ended with

int main() {
  ...
#if _DEBUG
  LOG_INFO("end, press key to close");
  getchar();
#endif // _DEBUG
  return 0;
}

Solution used in qtcreator pre 2.6. Now while qt is growing, vs is going other way. As I remember, in vs2008 we did not need such tricks.

answered Oct 15, 2014 at 14:35

just put as your last line of code:

system("pause");

answered Jan 9, 2018 at 22:59

Here’s a solution that (1) doesn’t require any code changes or breakpoints, and (2) pauses after program termination so that you can see everything that was printed. It will pause after either F5 or Ctrl+F5. The major downside is that on VS2013 Express (as tested), it doesn’t load symbols, so debugging is very restricted.

1. Create a batch file. I called mine runthenpause.bat, with the following contents:

   %1 %2 %3 %4 %5 %6 %7 %8 %9
   pause
   

   The first line will run whatever command you provide and up to eight arguments. The second line will… pause.

2. Open the project properties | Configuration properties | Debugging.

3. Change «Command Arguments» to $(TargetPath) (or whatever is in «Command»).
4. Change «Command» to the full path to runthenpause.bat.
5. Hit OK.

Now, when you run, runthenpause.bat will launch your application, and after your application has terminated, will pause for you to see the console output.

I will post an update if I figure out how to get the symbols loaded. I tried /Z7 per this but without success.

answered Nov 28, 2009 at 20:13

GeoGeo

91.8k115 gold badges343 silver badges516 bronze badges

Just press CNTRL + F5 to open it in an external command line window (Visual Studio does not have control over it).

If this doesn’t work then add the following to the end of your code:

Console.WriteLine("Press any key to exit...");
Console.ReadKey();

This wait for you to press a key to close the terminal window once the code has reached the end.

If you want to do this in multiple places, put the above code in a method (e.g. private void Pause()) and call Pause() whenever a program reaches a possible end.

answered Jan 30, 2015 at 19:48

A somewhat better solution:

atexit([] { system("PAUSE"); });

at the beginning of your program.

Pros:

• can use std::exit()
• can have multiple returns from main
• you can run your program under the debugger
• IDE independent (+ OS independent if you use the cin.sync(); cin.ignore(); trick instead of system("pause");)

Cons:

• have to modify code
• won’t pause on std::terminate()
• will still happen in your program outside of the IDE/debugger session; you can prevent this under Windows using:

extern "C" int __stdcall IsDebuggerPresent(void);
int main(int argc, char** argv) {
    if (IsDebuggerPresent())
        atexit([] {system("PAUSE"); });
    ...
}

answered Oct 23, 2017 at 20:37

AAEMAAEM

1,8272 gold badges17 silver badges26 bronze badges

0xsteve0xsteve

1011 silver badge4 bronze badges

user1323995user1323995

1,1761 gold badge9 silver badges16 bronze badges

JuanJuan

15.1k23 gold badges99 silver badges184 bronze badges

KANJICODERKANJICODER

3,47729 silver badges16 bronze badges

GáborGábor

9,0873 gold badges59 silver badges77 bronze badges

Go to Setting>Debug>Un-check close on end.

answered Jun 27, 2020 at 16:32

You can simply press Ctrl+F5 instead of F5 to run the built code. Then it will prompt you to press any key to continue. Or you can use this line -> system("pause"); at the end of the code to make it wait until you press any key.

However, if you use the above line, system("pause"); and press Ctrl+F5 to run, it will prompt you twice!

Yes, in VS2010 they changed this behavior somewhy.
Open your project and navigate to the following menu: Project -> YourProjectName Properties -> Configuration Properties -> Linker -> System. There in the field SubSystem use the drop-down to select Console (/SUBSYSTEM:CONSOLE) and apply the change.
«Start without debugging» should do the right thing now.

Or, if you write in C++ or in C, put

system("pause");

at the end of your program, then you’ll get «Press any key to continue…» even when running in debug mode.

answered Nov 7, 2010 at 14:16

answered Nov 7, 2010 at 14:17

You could open a command prompt, CD to the Debug or Release folder, and type the name of your exe. When I suggest this to people they think it is a lot of work, but here are the bare minimum clicks and keystrokes for this:

• in Visual Studio, right click your project in Solution Explorer or the tab with the file name if you have a file in the solution open, and choose Open Containing Folder or Open in Windows Explorer
• in the resulting Windows Explorer window, double-click your way to the folder with the exe
• Shift-right-click in the background of the explorer window and choose Open Commmand Window here
• type the first letter of your executable and press tab until the full name appears
• press enter

I think that’s 14 keystrokes and clicks (counting shift-right-click as two for example) which really isn’t much. Once you have the command prompt, of course, running it again is just up-arrow, enter.

answered Nov 7, 2010 at 17:40