[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [pygame] Segmentation Fault?

Hi Anthony,

Well, the thing is that to reproduce the crash I went through around five minutes of navigating the game, which is itself several thousand lines long. And there are 4 MB of graphics to sift through as well. So I didn't think it a very good idea.

I was in the process of cutting out the problem code into a smaller script for display purposes when I decided to try resetting the colourkey of the surface to blit. I don't know why I thought of that, and I don't know why it works, but...it does work.

Thanks anyway,

----- Original Message ----- From: "Anthony Baxter" <anthony@interlink.com.au>
To: <pygame-users@seul.org>
Sent: Thursday, November 25, 2004 4:00 PM
Subject: Re: [pygame] Segmentation Fault?

On Thursday 25 November 2004 15:54, Glen Wheeler wrote:
Strange since I am used to seeing much more helpful python tracebacks.
Anyway, the function blitToBG simply takes a surface and a position then
blits the two. The function is used many more times than just that one
time! The thing fails at the same place every time. In fact, the function
blitToBG is so simple I'm placing it here:
That code doesn't crash for me. If you can produce a complete
script that causes the crash, it's much more likely that someone
could fix it. I'm guessing it's a problem in the pygame extensions
rather than in python itself.