"SFML works!" tutorial not working

[R3B3LCAUSE]

Sorry it took so long, I've been busy.

-------------- Clean: Debug in Test ---------------

Cleaned "Test - Debug"

-------------- Build: Debug in Test ---------------

mingw32-g++.exe -Wextra -Wall  -g    -I"C:\[edit]\SFML-2.1\include" -I"C:\[edit]\SFML-2.1\include"  -c "C:\Program Files (x86)\CodeBlocks\Developement Space\Test\Main.cpp" -o obj\Debug\Main.o
mingw32-g++.exe -L"C:\[edit]\SFML-2.1\lib" -L"C:\[edit]\SFML-2.1\lib"  -o "bin\Debug\Test.exe" obj\Debug\Main.o    -lsfml-graphics-d -lsfml-window-d -lsfml-system-d  -mwindows
Output size is 748.38 KB
Process terminated with status 0 (0 minutes, 2 seconds)
0 errors, 0 warnings

What error are you referring to? The program doesn't open at all, there is no error message. Trying to run it from CodeBlocks gives this

Process terminated with status -1073741819 (0 minutes, 19 seconds)

and the debugger still shows the same "segmentation fault"

[R3B3LCAUSE]

Bump. Still need help

[eXpl0it3r]

It's not clear. Does the process ever start (check with task manager)?
What if you run it through the debugger?

Have you made a clean rebuild?

[R3B3LCAUSE]

It does show up in task manager, but it dies quickly.
Ive run it through the debugger, as I said, and it reports a "segmentation fault"

I have rebuilt it several times, every time i make a change

[eXpl0it3r]

Where exactly does it show that error code?

When run through the debugger it should jump to the part where the error originates from?

[R3B3LCAUSE]

Where exactly does it show that error code?

When run through the debugger it should jump to the part where the error originates from?

I'm sorry, I'm not sure what you mean by "error code"; there is no error message that pops up, the CodeBlocks build log shows the "Process terminated with status -1073741819 (0 minutes, 19 seconds)", and the debugger says that there is a "Segmentation Fault" but I'm not sure what that means.

[wintertime]

That means a fault got triggered inside the CPU, because the program was accessing unaccessible/nonexistent/unallocated memory.
You could look if the debugger shows a source line where it happens or single step the program to find it.