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=4696          
     

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|amaroK crashes mach64/no-DRI|segfault in server-side
                   |X server on ATI Rage LX Pro |glXMakeCurrent path with
                   |                            |indirect rendering




------- Additional Comments From [EMAIL PROTECTED]  2005-10-05 14:27 -------
It's often *very* difficult to get useful information from inspecting variables
when you build with optimization.  My guess is that you get a bogus value for cl
in __glXMakeCurrent because of this.  Please rebuild with this line in your
config/cf/host.def file and try to reproduce the segfault:

#define DefaultGcc2i386Opt -O0 -ggdb3

After you rebuild, you will only need to do this command to install the relevent
modules:

install -m 444 exports/libs/modules/extensions/lib{glx,GLcore}.so \
   /usr/X11R6/lib/modules/extensions

I've also updated the bug summary.  I suspect that after we get a little more
information we'll change the product / component as well.  My guess is that the
problem is in the server-side GLX protocol layer and not in core Mesa.
          
     
     
--           
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.


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
--
_______________________________________________
Dri-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to