Messages

1

General / Re: segfault when call draw

« on: December 31, 2014, 07:09:19 pm »

It was c++ but everything was linked. It compiled just fine it's just when it runs it gets the segfault. I will post the code dump later as I have to figure out why it was saying that it can't write a file to a read only filesystem, can't even move files to the desktop via the mv command in terminal

2

General / Re: segfault when call draw

« on: December 31, 2014, 07:55:30 am »

I downloaded the Linux copy not the source, I just made sure everything was linked correctly in code::blocks an still same results. I did try to load a texture and try to display it, file loaded and I even tried changing the file to make it not detect the right file for the error message and it displayed the error, the problem there was still the ".draw(sprite);". Jesper, I have SFML 1.6 on my PowerMac g5 and the code from the tutorial works on that, except when I tried to follow a tutorial on loading tile maps using fstream (that is a bug with xcode 3.1 not allowing me to use fstream). I only asked if it was the operating system because as I stated when I was searching the forums for a thread with my problem someone had the same code on Linux and windows and windows worked and Linux had the segfault. I read somewhere that it may very well be Linux, not the operating system itself but their graphics driver isn't really the best as far as I read. Plus I know just enough Linux to get me by, I had to switch to Linux because my computer wasn't responding to a fresh install of windows 7. I tried getting the core dump, it worked but now I cant do it again, I will mess with it more tomorrow and post my core dump.

You guys also forgot something: my code won't compile! I have to buy a new computer and try again 

3

General / segfault when call draw

« on: December 30, 2014, 07:09:20 am »

When I try to test SFML 2.2 by using the example code in the tutorials. I have followed every step and when I try to run it I get "Segmentation fault (core dumped)". I have found that it is whenever I call the ".draw()" command, it would run without the segfault if I commented that line out. I am running Ubuntu 14.04 using Code::Blocks to write and run my code. I looked around the forum and there were similar issues where people had segfaults when using fonts using Linux and when they went to windows they had it working same code. Could it be Linux that is causing this, should I do switch back to windows?