Re: [pygame] pygame.mixer crashes

[Charles Joseph Christie II <sonicbhoc@xxxxxxxxx>]

That's odd, it worked perfectly for me on my PCLinuxOS box. If you look
at the PCLinuxOS forums, you can find a thread where I (sonicbhoc) ask
for a pygame rpm and someone provides one for me. It works fine over
here. Also, did you try updating to Test Release 3?

On Mon, 5 Mar 2007 15:39:47 -0800 (PST)
"Ðáíáãéþôçò" "ÔóéìðÝñçò" <takira_gr@xxxxxxxxx> wrote:

> Rikard here it goes
> 
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread -1480189728 (LWP 18930)]
> 0xa7ccd0e3 in strlen () from /lib/i686/libc.so.6
> (gdb) bt
> #0  0xa7ccd0e3 in strlen () from /lib/i686/libc.so.6
> #1  0xa7653594 in open_file () from
> /usr/lib/libSDL_mixer-1.2.so.0
> #2  0xa765da72 in Timidity_Error () from
> /usr/lib/libSDL_mixer-1.2.so.0
> #3  0xa765e521 in Timidity_Init () from
> /usr/lib/libSDL_mixer-1.2.so.0
> #4  0xa763a3aa in open_music () from
> /usr/lib/libSDL_mixer-1.2.so.0
> #5  0xa76386f9 in Mix_OpenAudio () from
> /usr/lib/libSDL_mixer-1.2.so.0
> #6  0xa772060e in autoinit (self=0x0, arg=0xa7c2102c)
> at src/mixer.c:184
> #7  0xa7e22f2b in PyCFunction_Call () from
> /usr/lib/libpython2.4.so.1.0
> #8  0xa7dfaf89 in PyObject_Call () from
> /usr/lib/libpython2.4.so.1.0
> #9  0xa7e5698e in PyEval_CallObjectWithKeywords ()
>    from /usr/lib/libpython2.4.so.1.0
> #10 0xa7dfbad9 in PyObject_CallObject () from
> /usr/lib/libpython2.4.so.1.0
> #11 0xa7fd095a in init (self=0x0, args=0xa7c2102c) at
> src/base.c:197
> #12 0xa7e22f2b in PyCFunction_Call () from
> /usr/lib/libpython2.4.so.1.0
> #13 0xa7e5c367 in PyEval_EvalFrame () from
> /usr/lib/libpython2.4.so.1.0
> #14 0xa7e5cfd6 in PyEval_EvalCodeEx () from
> /usr/lib/libpython2.4.so.1.0
> #15 0xa7e5d045 in PyEval_EvalCode () from
> /usr/lib/libpython2.4.so.1.0
> #16 0xa7e776da in Py_CompileString () from
> /usr/lib/libpython2.4.so.1.0
> #17 0xa7e791f9 in PyRun_InteractiveOneFlags ()
>    from /usr/lib/libpython2.4.so.1.0
> #18 0xa7e79310 in PyRun_InteractiveLoopFlags ()
>    from /usr/lib/libpython2.4.so.1.0
> #19 0xa7e7943e in PyRun_AnyFileExFlags () from
> /usr/lib/libpython2.4.so.1.0
> ---Type <return> to continue, or q <return> to quit---
> #20 0xa7e7fa71 in Py_Main () from
> /usr/lib/libpython2.4.so.1.0
> #21 0x08048641 in main ()
> (gdb)
> 
> Thank u guys 4 the replies
> 
> --- Rikard Bosnjakovic <rikard.bosnjakovic@xxxxxxxxx>
> wrote:
> 
> > On 3/4/07, Ðáíáãéþôçò ÔóéìðÝñçò
> > <takira_gr@xxxxxxxxx> wrote:
> > 
> > > In fact I don't think it's a mixer problem at all:
> > [...]
> > 
> > Instead of python, issue "gdb python" and then
> > "run". Then do the
> > imports and the like you did above.
> > 
> > When you get SIGSEGV and return to gdb, type "bt"
> > (backtrace) to see
> > where the crash occurs.
> > 
> > 
> > -- 
> > - Rikard.
> > 
> 
> 
> 
>  
> ____________________________________________________________________________________
> The fish are biting. 
> Get more visitors on your site using Yahoo! Search Marketing.
> http://searchmarketing.yahoo.com/arp/sponsoredsearch_v2.php