libGL bug in your source tree?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi, I am thinking that there may be a bug in libGL in your XFree project...

In xc/lib/GL/glx/glxext.c, AllocAndFetchScreenConfigs:

line 979 locks the display: LockDisplay(dpy);
then line 1013 unlocks the display once: UnlockDisplay(dpy);
... but the code which follows line 1013 (e.g. any of the lines: 1016,
1028, 1038, 1083) will result in double unlocking (i.e. unlocking the
already unlocked display which on some systems such as
NetBSD-current's macppc port raises the "unlocking already unlocked
mutex" error and the process is killed).

My suggestion is to take out line 979.
The following (albeit from Mesa) file in OpenBSD repository appears to
have it solved:
http://www.openbsd.org/cgi-bin/cvsweb/xenocara/dist/Mesa/src/glx/x11/glxext.c?rev=1.2&content-type=text/x-cvsweb-markup

Am sorry if I am mistaken in thinking that it is a bug in XFree's
libGL, if so, however - can anyone explain why line 979 (and
subsequent double unlocking of the display) is actually needed in the
first place?
_______________________________________________
Devel mailing list
Devel@xxxxxxxxxxx
http://XFree86.Org/mailman/listinfo/devel

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [X Forum]     [XFree86]     [XFree86 Newbie]     [X.Org]     [IETF Annouce]     [Security]     [Fontconfig]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]

  Powered by Linux