PyWeek - SegFault Error

Hi, im' using WinXP, python2.5, pygame1.7 around 4-5 games have crashed while running with the Segfault message. Does anybody else face this problem? ill' post the names of the games which crashed a little later.

— gizmo_thunder on 2007/04/13 06:23 of Gizmo

Comments: (log in to comment)

By gizmo_thunder on 2007/04/13 06:32:

Exact error message:
Fatal Python error: (pygame parachute) Segmentation Fault This application has requested
the Runtime to terminate it in an unusual way. Please contact the application's support team
for more information.
Games which cause this error:

By simono on 2007/04/13 10:29:

had the same problem with XP,py25,pygame17, all three games work fine in linux.

By mcferrill on 2007/04/13 11:11:

I had to run those games in python 2.4 (XP, pygame 1.7.1), but I'm pretty sure the problem's in run_game.py as my tweaked version works fine in 2.5.

By RB[0] on 2007/04/13 17:36:

gizmo: I couldnt run any of those either, or a few others :(
I dont think it is a run_game.py skellington thing though, I think this a pygame or python error, I dont have time right now to ferret out the problems, but I'll try this weekend.

I'll also see what other ones are doing this on me...

I'll also test python 2.4, as the only time that version seg-faulted for me was when using pygame surfarrays.

By Hex Decimal on 2007/04/13 18:58:

I use XP and py2.5 and I had a few problems like this also.
The problem for me was that pygame would crash after it was given a file like object to things like pygame.image.load
I fixed it by replacing most of the data.load calls relating to images by a data.filepath call.

By RB[0] on 2007/04/13 19:30:

Ahh, I ran into that in one of the games, and fixed it,
were you able to fix them all by changing that?

By Hex Decimal on 2007/04/13 20:28:

Most of the games with this error just loaded the graphics as a file and passed it directly to pygame.
So yes, I was able to fix every game I played so far.

By richard on 2007/04/13 21:40:

Please report this as a bug to the pygame maintainers - it won't get fixed otherwise!

By RB[0] on 2007/04/13 23:17:

I dont think this is a pygame bug...

its a bug when someone does something like:
    image=pygame.image.load(open(filename,'r'))
instead of just:
    image=pygame.image.load(filename)
I dont think this should be a "pygame" error, it is an error when ppl misuse the skellington.
So... ppl just need to use the path to the file, instead of opening it and then sending it to pygame :)

By pekuja on 2007/04/13 23:44:

Well it is a pygame error in the sense that it's segfaulting. It should throw an exception instead so that the program can properly exit without crashing.

By richard on 2007/04/14 01:48:

What pekuja said :)