Cannot print Hello World statement in Visual Studio Code - c++

So I am really new when it comes to C++, and have tried learning it.
So far I have installed the MINGW64 MYSYS2 thing for the gcc, gdb and g++ (compilers?). And have created my workspace.
Whenever I try to print the "Hello World" statement, it won't print it for some reason? I really have no idea what I am doing wrong. Can someone please help.
Code:
#include <iostream>
int main() {
std::cout << "Hello World";
return 0;
}
Output:
* Executing task: C/C++: g++.exe build active file
Starting build...
"C:\Program Files\Haskell Platform\8.6.5\mingw\bin\g++.exe" -fdiagnostics-color=always -g "C:\Users\bsdwi\Documents\Visual Studio 2017\C C++\HelloWorld\HelloWorld.cpp" -o "C:\Users\bsdwi\Documents\Visual Studio 2017\C C++\HelloWorld\HelloWorld.exe"
Build finished successfully.
* Terminal will be reused by tasks, press any key to close it.
Followed by this pop-up message:
error message
Has it got something to do with the Haskell thing? I am so new to Visual Studio Code and C++ so I'd really appreciate any help.
And apologies in advance if I have missed something out that you guys need in order to help me. Please let me know if you require more information.

Related

gdb <error reading variable> for any string object

Lets take this very simple program here for example:
// test.cpp
#include <string>
#include <iostream>
using namespace std;
int main() {
string str = "Hello";
cout << str << endl;
return 0;
}
now I compile this code with g++ compiler:
g++ -g test.cpp -o test.exe
now I am trying to debug this with gdb:
gdb test.exe
after I set breakpoint on main and then reach the line return 0, I try to see what is in the string str. But I cannot print it in the console. It says <error reading variable>. Not only in gdb console, even Visual Studio Code UI using gdb gives the same output.
Here is a screenshot of my console:
I have searched for this everywhere and the only relevant question I found was this, which did not work.
I also found this post on github VS Code repo issues. The fix suggested there might work I am not sure, I cannot find the setting that he suggested on my Windows 11 machine.
How do I read the value in the string in debug mode?
Edit
After #ssbssa suggested me to update my gcc, I used MSYS2 to get the latest gcc, g++, and gdb versions. Now I have gdb 12.1. Now it is not showing the old error anymore but now it says "Converting character sets: Invalid argument". Still struggling to get it to work.
First run your program with gdb like so:
gdb test.exe
Now inside the command line interface run the command:
set charset UTF-8
This should temporarily fix your problem. The only inconvenience might be that you need to run this line every time you debug on your command prompt with GDB.
I noticed that you are also using Visual Studio Code. You can install C++ extensions for VS Code and there you can add the command set charset UTF-8 in the launch.json setupCommands array as shown here. This way you can debug your application faster.

Compiling Hello World C++ Code in Visual Studio Code

I have a very simple hello world code as shown below:
#include <iostream>
int main()
{
std::cout << "Hello World!";
return 0;
}
I am trying to compile it in VSCode powershell terminal of Windows 10. I am using VS Community 2019.
Here is my directory structure:
When I do a cl triplex.cpp I get this:
but then at the next step when I try to run the program:
triplex
I am getting this error:
I have seen many posts with this error but none of them actually solved up my issue. Someone please help me getting out of this problem.
As suggested by #d4rk4ng31, It executed using ./triplex. Thank you so much guys.
its very simple download mingw installer ,set its path in environment variable,for compiling in vscode just type command:-
g++ (name of file).cpp
2nd command :-
a.exe

Necessary extensions for VS code with Windows OS

I am a first time C++ user, and I have been working for 8 hours trying to build and compile the simple "Hello World" program with C++ in Visual Studio Code. I have CygWin64, but I'm not sure if it's connected to my VSCode. I have installed the extensions C/C++, C/C++ Compile Run, C++ Intellisense, Clang-Format, and Easy C++ projects.
So far I have tried
#include <iostream.h>
main()
{
cout<< "Hi there";
return 0;
}
and
#include <iostream.h>
int main() {
std::cout << "Hello Easy C++ project!" << std::endl;
}
Using iostream.h helped me to get to work (it wouldn't at first), but I'm not sure if that is helpful, since other posts say that .h is very archaic. I have also tried editing my c_cpp_properties.json file. Sadly, I still get the message:
"> Executing task: bash -c "make run" <
'bash' is not recognized as an internal or external command,
operable program or batch file.
The terminal process terminated with exit code: 1
Terminal will be reused by tasks, press any key to close it."
I am not sure if I need to install an alternative to Clang (I haven't found one), or run something initially on Cygwin64.
I have been looking online for suggestions and following pages such as https://dev.to/acharluk/developing-c-with-visual-studio-code-4pb9 and https://github.com/Microsoft/WSL/issues/1598, but I still can't seem to get around this problem.
Any help would be very appreciated.
Thanks,
Anne

"Hello world!" freeze in c++

I tried to compile a simple Hello World in C++ to test that my Visual Studio 2013 on my Windows 10 works well but I've a problem. My program compile but when I run, it freeze. It's an empty Win32 Console Application with a "main.cpp" :
#include <iostream>
using namespace std;
int main()
{
cout << "Hello world!";
return 0;
}
If I launch it from Visual Studio in debug (with "Run"), Visual Studio freeze and I need to kill its task.
If I launch it with the executable or with "Run without Debugging", nothing appear, "System" process doesn't want to free the execution and I can't recompile without restart the computer because of that.
I am confused. If somebody have an idea of what's happening, please help me.
Update 1 : I repair my installation. Same problem. Breakpoint doesn't help. It seems to freeze before. And also no trace of a task in the task manager when launched without debugging.
It was my antivirus' fault (in my case, Avast). I made it ignore my Visual Studio projects and it works. Solved by #Blastfurnace.

Notepad++, NppExec, CreateProcess() failed with error code 2, Windows 8.1

I'm new to Notepad++ and C++ programming language. I couldn't figure out what has gone wrong, albeit, it might look simple to resolved to many.
Tried to search for solution, but to no avail.
While trying to config the application for C++ compiler on Windows 8.1, I encountered the below message.
NPP_SAVE: C:\Users\rolle_000\Desktop\HelloWorld.cpp
CD: C:\Users\rolle_000\Desktop
Current directory: C:\Users\rolle_000\Desktop
Compiled.exe -c -w "HelloWorld.cpp"
CreateProcess() failed with error code 2:
The system cannot find the file specified.
================ READY ================
The C++ basic code, simple to testing only.
// A hello world program in C++
#include<iostream>
using namespace std;
int main()
{
cout << "Hello World!";
return 0;
}
The NppExec script taken from
How to compile and run C files from within Notepad++ using NppExec plugin?
Below embedded mine, script hasn't change much.
NPP_SAVE
CD $(CURRENT_DIRECTORY)
Compiled.exe -c -w "$(FILE_NAME)"
Pls advice, thank you.
You're trying to execute a
Compiled.exe
which indeed doesn't exist (yet) instead of the
perl.exe -c -w "$(FILE_NAME)"
perl.exe is the perl's executable and is supposed to be used with a perl's program. To compile C++ programs you will need to use a C++ compiler.
Now: this all boils down to the compiler you want to use... which one are you going to use? MSVC (Microsoft Visual Studio) ? Bloodshed dev-cpp?
Example: if you have MSVC2010 installed you might use:
Execute Start->All Programs->Microsoft Visual Studio 2010->Visual Studio Tools->Visual Studio Command Prompt (2010)
Digit cl (yourFileName).cpp
You're done, yourFileName.exe should now exist
So the above would have to be rewritten as:
cl.exe "$(FILE_NAME)"
after making sure the path to cl.exe is correctly available.