> Aapo Tahkola wrote: >> Hi. >> >> I noticed that Vladimirs adition to struct r300_state caused arbvptorus >> to >> get broken pretty badly. This is pretty much similar to the bug where vb >> mode color buffer clears were broken. >> Iv been trying to figure out this for a while now with no success and I >> was thinking if anyone else would like to give it a shot. >> I traced its causer down the structures to struct r300_dma before struct >> r300_dma_region current;. This doesnt exactly mean that its in dma code >> but at least its a start. >> >> Unfortunately i havent found anything useful in compiler warnings and im >> currectly lacking ideas of how to find it... >> > I would like to give it a try, but I need a simple program that triggers > it.
Mesa/progs/tests/arbvptorus.c is pretty much as simple as it can get. You could comment instructions after the first four DP4s and calls to glProgramLocalParameter4fARB later. Its pretty strange that when removing usage of vertex program from the example these problems go away. I didnt test with per-vertex colors though. By replacing "glutSolidTorus(0.75, 2.0, 10, 20)" with a "glutSolidTeapot(4);" you should see some errors when resizing the window. I think this is a pretty good sign in sense that fixing this might actually affect general stability of vb mode. (i had similar issues and lockups when trying to make fire_EB work) You can temporarily "fix" this by moving "int dummy;" in struct r300_dma below current as said in comments. > > > Rune Petersen -- Aapo Tahkola ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&op=click -- _______________________________________________ Dri-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dri-devel
