Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=7117
------- Additional Comments From [EMAIL PROTECTED] 2006-06-17 14:07 -------
Hmm, yes, I see. Especially the unregular lockups are awful to identify. :-(
Two ideas that I'd like to discuss:
1.) insert error debug messages into the dri driver, e.g. writing some status
information to syslog, so that one might be able to find out at least in what
function the freeze happens?
2.) Don't write the syslog messages to the disk, but broadcast them on the
network and log them on a second computer?
But maybe it is simpler to start with a more regular freeze such as bug #7154.
This one is easily reproducible and I guess the developers might be able to make
some educated guesses in what function such a freeze might happen. Then with the
above approach we might be able to identify the function, which may be a start
to find the error...
Unfortunately this bug here is the most problematic at the moment as it occurs
when any OpenGL app is running (last freeze was with Google Earth). Without
finding it, xgl won't be usable. :(
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
