Michel Dänzer wrote: > One possibility could be that it's triggering undetected GL error > conditions. With a Mesa debugging build, there's a message on stderr > every time a GL error condition is triggered. Or you could try attaching > gdb and setting a breakpoint at _mesa_error. >
Mesa: Mesa 7.1 rc3 DEBUG build Aug 7 2008 21:18:34 Mesa warning: couldn't open libtxc_dxtn.so, software DXTn compression/decompression unavailable *********************************WARN_ONCE********************************* File r300_render.c function r300Fallback line 371 Software fallback:ctx->RenderMode != GL_RENDER *************************************************************************** And that's all. The WARN_ONCE appears as soon as I move mouse pointer into the black draw area. RenderMode in question is GL_SELECT. I verified by digging in /proc/<pid>/maps that r300_dri.so loaded is indeed the one from the debug build. Unfortunately I could not force gdb to load symbols. Is there anything that can be done short of constructing a testcase based on wine GL function call trace? ./lxnt ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Mesa3d-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
