Re: [pygame] Segmentation fault in pygame.mixer

[Rene Dudfield <renesd@xxxxxxxxx>]

Hey Rudá,

ooh.  pygame on ARM! hehe

Could you please try using the cvs pygame?  It's probably broken too,
but you never know.

If you have time, you could start putting print statements in the quit
function. Then run it and see which print statements are printed. 
Then you can tell us where it crashes.


Cheers.




On 7/28/05, Rudá Moura <ruda.moura@xxxxxxxxxxx> 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:
> 
> ---
> 
> Python 2.4.1 (#1, Jul 27 2005, 15:35:49)
> [GCC 3.3.4 (Debian)] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
> >>> import pygame
> >>> pygame.mixer.init()
> Traceback (most recent call last):
>   File "<stdin>", line 1, in ?
> pygame.error: No available audio device
> >>> pygame.mixer.quit()
> >>>
> Segmentation fault
> 
> ---
> 
> I have the following packages installed:
> - Python 2.4.1
> - PyGame 1.6
> - libsdl-mixer 1.2.6
> - libsdl 1.2.8
> 
> This just happens in ARM architecture, I have the same versions for i386
> and everything works just fine.
> 
> I'm debugging it now but I guess its about not counting objects
> references in pygame module when quitting. Any other clue?
> 
> Oh, this is what gdb gives me...
> 
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 16384 (LWP 873)]
> 0x40afa2dc in ?? ()
> (gdb) bt
> #0  0x40afa2dc in ?? ()
> Cannot access memory at address 0x0
> (gdb)
> 
> yes, I compiled pygame, python, sdl-mixer with debug options (-g -O0).
> 
> Thank you!
> 
> --
> Rudá Moura
> 
>