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=8443          
     
           Summary: MakeContextCurrent may use the wrong opcode
           Product: Mesa
           Version: CVS
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: GLX
        AssignedTo: [email protected]
        ReportedBy: [EMAIL PROTECTED]


When a thread switches from one Display to another, I think glxext.c currently
uses the same major opcode for both Displays, because it uses the new Display to
get the old opcode:

    opcode = __glXSetupForCommand(dpy);
    ...
    oldOpcode = (gc == oldGC) ? opcode : __glXSetupForCommand(dpy);

I think the following patch fixes the problem:

--- glxext.c    26 Sep 2006 23:56:20 -0000      1.25
+++ glxext.c    27 Sep 2006 22:38:19 -0000
@@ -1582,7 +1582,7 @@ USED static Bool MakeContextCurrent(Disp
     }
 
     oldGC = __glXGetCurrentContext();
-    oldOpcode = (gc == oldGC) ? opcode : __glXSetupForCommand(dpy);
+    oldOpcode = (gc == oldGC) ? opcode : 
__glXSetupForCommand(oldGC->currentDpy);
     if (!oldOpcode) {
        return GL_FALSE;
     }          
     
     
--           
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.

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Mesa3d-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev

Reply via email to