Xi: Fix up ProcIVector, got out of sync with the protocol.
When the opcode squash happened in the protocol, the processing vector got out of sync for a few requests. As a result, client and server would interpret requests differently, leading to a couple of BadLength problems.
This commit is contained in:
parent
1fc1a2897e
commit
59b8d29b3a
20
Xi/extinit.c
20
Xi/extinit.c
|
@ -212,11 +212,11 @@ static int (*ProcIVector[])(ClientPtr) = {
|
||||||
ProcXWarpDevicePointer, /* 37 */
|
ProcXWarpDevicePointer, /* 37 */
|
||||||
ProcXChangeDeviceCursor, /* 38 */
|
ProcXChangeDeviceCursor, /* 38 */
|
||||||
ProcXChangeDeviceHierarchy, /* 39 */
|
ProcXChangeDeviceHierarchy, /* 39 */
|
||||||
ProcXiSelectEvent, /* 40 */
|
ProcXChangeWindowAccess, /* 40 */
|
||||||
ProcXChangeWindowAccess, /* 41 */
|
ProcXQueryWindowAccess, /* 41 */
|
||||||
ProcXQueryWindowAccess, /* 42 */
|
ProcXSetClientPointer, /* 42 */
|
||||||
ProcXSetClientPointer, /* 43 */
|
ProcXGetClientPointer, /* 43 */
|
||||||
ProcXGetClientPointer, /* 44 */
|
ProcXiSelectEvent, /* 44 */
|
||||||
ProcXExtendedGrabDevice /* 45 */
|
ProcXExtendedGrabDevice /* 45 */
|
||||||
};
|
};
|
||||||
|
|
||||||
|
@ -262,11 +262,11 @@ static int (*SProcIVector[])(ClientPtr) = {
|
||||||
SProcXWarpDevicePointer, /* 37 */
|
SProcXWarpDevicePointer, /* 37 */
|
||||||
SProcXChangeDeviceCursor, /* 38 */
|
SProcXChangeDeviceCursor, /* 38 */
|
||||||
SProcXChangeDeviceHierarchy, /* 39 */
|
SProcXChangeDeviceHierarchy, /* 39 */
|
||||||
SProcXiSelectEvent, /* 40 */
|
SProcXChangeWindowAccess, /* 40 */
|
||||||
SProcXChangeWindowAccess, /* 41 */
|
SProcXQueryWindowAccess, /* 41 */
|
||||||
SProcXQueryWindowAccess, /* 42 */
|
SProcXSetClientPointer, /* 42 */
|
||||||
SProcXSetClientPointer, /* 43 */
|
SProcXGetClientPointer, /* 43 */
|
||||||
SProcXGetClientPointer, /* 44 */
|
SProcXiSelectEvent, /* 44 */
|
||||||
SProcXExtendedGrabDevice /* 45 */
|
SProcXExtendedGrabDevice /* 45 */
|
||||||
};
|
};
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue
Block a user