On Thu, 2003-10-30 at 17:08, Chris Ison wrote:
I'm wondering what happened to the full sw mode for 3d you could use before when DRI wasn't enabled. Now GL apps just seg (including glxgears) where a few months ago you could still run them without DRI although very slow.
Further investigation has shown glXSwapBuffer is the where the seg is coming from ...
164 glXSwapBuffers (x_disp, x_win);
(gdb) p x_disp
$1 = (Display *) 0x84514a0
(gdb) p x_win $2 = 31457282
(gdb) n
Program received signal SIGSEGV, Segmentation fault.
0x00000000 in ?? ()
(gdb)
Do you get the same behavior if DRI is enabled, but you run with 'LIBGL_ALWAYS_INDIRECT=y'? Since the back trace isn't clean, it looks like there some stack corruption happening. I'll see if I can reproduce it tomorrow (I don't have access to an R200 at the moment), but I don't see this on an MGA. If DRI isn't loaded, it shouldn't matter what the hardware is. You might try stepping through glXSwapBuffers to see where it explodes.
I suspect you have some thing built wrong or there's some sort of version incompatability. What's the rest of your system? There were some problems with recent libGL.so binaries and RedHat TLS enabled systems, but I *thought* those were fixed (they were all my fault anyway).
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
