[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [pygame] Segmentation fault in pygame.mixer
- To: pygame-users@xxxxxxxx
- Subject: Re: [pygame] Segmentation fault in pygame.mixer
- From: Rudá Moura <ruda.moura@xxxxxxxxxxx>
- Date: Fri, 05 Aug 2005 13:46:55 -0300
- Delivered-to: archiver@seul.org
- Delivered-to: pygame-users-outgoing@seul.org
- Delivered-to: pygame-users@seul.org
- Delivery-date: Fri, 05 Aug 2005 12:47:16 -0400
- In-reply-to: <1122557672.13319.13.camel@localhost.localdomain>
- Organization: Instituto Nokia de Tecnologia
- References: <1122557672.13319.13.camel@localhost.localdomain>
- Reply-to: pygame-users@xxxxxxxx
- Sender: owner-pygame-users@xxxxxxxx
On Thu, 2005-07-28 at 10:34 -0300, Rudá Moura wrote:
> Hello everybody,
>
> I don't know if it is a know issue (or I'm doing something wrong!), but
> I'm getting segmentation fault
> in pygame.mixer whenever I do a init(), quit() and exit from Python
> interpreter, like:
Hi!
I have two good news:
- First, I found the bug!
- Second, it was not PyGame guilt. (as expected) :)
My Python 2.4 development package sets -O3 to compile python modules and
I have just discovered (debugging) strange behavior in autoinit() and
autoquit() when stepping in statements, so I decide to disable
optimizations. I compiled PyGame with -O0 and the segmentation was gone!
Great, but without optimizations is no good for game developers, so I
decide to recompile with -O2. It works! No segmentation faults.
Don't know if it was the GCC compiler (3.3.5) for ARM or the scratchbox
(build tool) environment but I will use -O2 for now and then.
Thanks and keep working on PyGame!