There is no error here, except as others have mentioned the non-zero
return value from your program which would imply there is at least one
exit(1); call in your project or a return 1; statement in the "main"
function. C and C++ programs generally return 0 on success and
non-zero for some failure.
The output above is from the Visual Studio IDE "Output" window that is
filled in by the debugger as it starts up and runs your program. All
the DLLs are listed as they are loaded in support of your program.
There is generally no important information in the debug output window
unless you use functions like OutputDebugString() to print information
to it.
The [5668] is the process ID (PID) of your program for that session.
The PID will change every time your program is executed. CAS HYDRO
seems to be the program name but the last line seems a little odd to
me as it's not what I usually see. Sample below:
[many dll loads snipped]
The program '[4320] sigsegv.exe: Native' has exited with code 0 (0x0).
I seldom need support DLL symbols nor do I debug into the library DLLs
so I don't load their symbols anymore.
Paavo's suggestion of ctrl-F5 to run your program in a console window
detached from the debugger is an excellent one for console mode
programs with erroneous behaviors or unexpected terminations.
Otherwise, to track down your error return, set breakpoints at all
exit(1) or return 1; statements and run with debugger using F5 to see
where your program is terminating.