Dark Avenger wrote:
>
> Re: > 1) Seg. Fault and Xlib: unexpected async reply (sequence 0x1728)!
> Re:
> Re: I remember seeing problems like this when I was debugging multi-threaded
> Re: apps. Does XMMS use threads in conjunction with OpenGL?
>
> Yes sir, OpenGL + threads. The error above is,
Re: It's multithreaded, yes. The plugins generally run as separate threads.
Correct
Re: I did try the fix that Dark Avenger suggested, and that does clear up
Re: the problem with the OpenGL vis plugin causing XMMS to die.
Glad :)
Re: I just pulled the current XMMS CVS tree, and it looks l
Re: > 1) Seg. Fault and Xlib: unexpected async reply (sequence 0x1728)!
Re:
Re: I remember seeing problems like this when I was debugging multi-threaded
Re: apps. Does XMMS use threads in conjunction with OpenGL?
Yes sir, OpenGL + threads. The error above is, like you said due to concurrent
Derrik Pates wrote:
>
> Brian Paul wrote:
>
> > I remember seeing problems like this when I was debugging multi-threaded
> > apps. Does XMMS use threads in conjunction with OpenGL?
>
> It's multithreaded, yes. The plugins generally run as separate threads.
> I did try the fix that Dark Avenger
Brian Paul wrote:
> I remember seeing problems like this when I was debugging multi-threaded
> apps. Does XMMS use threads in conjunction with OpenGL?
It's multithreaded, yes. The plugins generally run as separate threads.
I did try the fix that Dark Avenger suggested, and that does clear up
Dark Avenger wrote:
>
> Subject: 5-10 lines of code. Do u see a bug?
>
> Using XMMS 1.2.5 and the plugin OpenGL Spectrum Analyzer 1.2.5 that comes with it
>gives errors on both X11 4.1.0 w/ DRI + tdfx driver and NVidia OGL driver. The errors
>are of type:
>
> 1) Seg. Fault and Xlib: unexpect
