Mouse <mouse%Rodents-Montreal.ORG@localhost> wrote:
> I've just run into what I consider to be a bug in an X server. I first
> saw with a relatively recent Ubuntu on a work machine, which prompted
> me to look for it elsewhere.
> I do not see it with the MIT server I use on 1.4T. I do not see it
> with the server built from 5.2's /usr/xsrc. But I *do* see it with the
> server built from 9.1's /usr/xsrc.
> The bug is that, when a client issues a ChangeGC request trying to set
> a clip-mask pixmap with 0x2000001a as the pixmap ID (not a valid ID; X
> resource IDs never have any of the top three bits set), the invalid ID
> value in the resulting error is 0 instead of 0x2000001a. (This
Like it has masked off those bits early, and then can't reply with the broken
resource ID. But, I guess if that was the case, it would say 0x1a... so..
I'm curious how you ran into this... some application that doesn't know the
limits of resource IDs?
I had to add #include <stdlib.h>, and I had to build with -lX11:
cc test-err-1.c -o test-err-1 -lX11
(I had done: "make test-err-1" at first)
obiwan-[~/src](3.3.8) mcr 10315 %./test-err-1
X Error of failed request: BadPixmap (invalid Pixmap parameter)
Major opcode of failed request: 56 (X_ChangeGC)
Resource id in failed request: 0x0
Serial number of failed request: 7
Current serial number in output stream: 9
version number: 11.0
vendor string: The X.Org Foundation
vendor release number: 12101007
X.Org version: 21.1.7
This is devuan Linux, so maybe redudant with your report of Ubuntu.
Attachment:
signature.asc
Description: PGP signature