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

Re: [pygame] Segmentation fault in pygame.mixer



ah excellent :)

Yeah any optimization above -O2 is not really safe to use.


On 8/6/05, Rudá Moura <ruda.moura@xxxxxxxxxxx> wrote:
> 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!
> 
> 
> 
>