I tried to do this from a remote machine and locally, and both times, I get errors like:I could reproduce your X lockups with my Radeon 7500 by disabling TCL (RADEON_TCL_FORCE_DISABLE=1) which is as close as I can get to your Radeon VE. I don't use the dri_resume patch. From your telling that it helped to kill the offending GL app it sounds like the GL app gets stuck somewhere while holding the lock. It would be helpful to know where exactly that is. Unfortunately I don't have a second system at hand to log in remotely from.Could you reproduce a lockup with a GL app running in a remote debugger session. When the system is locked up you press Ctrl+C in the debugger, get backtrace with the "bt" command and send it to the list.
**********************************************
$ gdb
GNU gdb 5.0
Copyright 2000 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-slackware-linux".
(gdb) exec-file /usr/local/lib/xscreensaver/endgame
(gdb) set args -display :0
(gdb) run
Starting program: /usr/local/lib/xscreensaver/endgame -display :0
warning: Unable to find dynamic linker breakpoint function.
GDB will be unable to debug shared library initializers
and track explicitly loaded dynamic code.
warning: shared library handler failed to enable breakpoint
Program received signal SIGFPE, Arithmetic exception.
0x404fc600 in ?? ()
(gdb) quit
The program is running. Exit anyway? (y or n) y
$
**********************************************
A window is created for the hack to run, but nothing ever appears.
It appears to me that I need to compile endgame (and/or other GL hacks) with debugging information. I don't know how to do this, though. If you could direct me to some information about how I would go about it, I'd much appreciate it.
I was reading a document later about graphics coding and it mentioned that erasing the image you wanted to move, and then redrawing it would produce flicker and the solution to this was double-buffering and it reminded me of the flickering I see when running the GL hacks. I tried, and when having xscreensaver run the hacks in the root window, I get flickering. Curiouser and curiouser.About the flickering when running endgame on the root window, I could reproduce that too, even with TCL enabled. It looks to me like it is using a single buffered visual in that case. Curiously this doesn't happen when xscreensaver runs endgame on the root window.
Thanks.
-Andy
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
