Ian Romanick wrote:
Certainly a bug. First thing of concern is whether it's the vtxfmt/codegen stuff which isn't threadsafe, but should get turned off at the first sign of multithreading.On Wed, Oct 23, 2002 at 12:27:57AM +0200, Charl P. Botha wrote:On Tue, Oct 22, 2002 at 03:12:52PM -0700, Ian Romanick wrote:On Tue, Oct 22, 2002 at 12:46:27AM +0200, Charl P. Botha wrote:Run glthreads with something like: glthreads -n 5
Here's an additional data point. If you move the call to glXDestroyContext to the end of draw_loop (and delete the other two calls), the program works as expected on the Radeon. The event_loop won't terminate, but I leave fixing that trivial bug as an exercise for the reader. :)Hrmmm, interesting. The reason I made this is to reproduce a bug in a much larger application where that kind of control (taking glxDestroyContext() INto the thread) is quite difficult. Ian, do you consider this to be a bug?It's a bug somewhere. :) I'm going to have to dig more before I can determine if the bug is in the app, the driver, or both. Brian or Keith: Do either of you have an opinion about this?
Keith
-------------------------------------------------------
This sf.net emial is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0002en
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
