nx-libs/nx-X11/programs/Xserver/record, branch pr/extend_manpage

record/set.c: silence cpp finding

2019-06-22T09:30:54+00:00

[nx-X11/programs/Xserver/record/set.c:361]: (warning) Possible null pointer dereference: stackIntervals stackIntervals is only NULL if nIntervals is 0, too. In that case memcpy will do nothing and so it is ok to pass NULL as source. But it is ugly nevertheless...

Use C99 designated initializers in various extension Replies

2019-02-28T22:13:49+00:00

commit cc5f09c86f7bea23b7546c3491b2c52ce8100a71 Author: Alan Coopersmith Date: Mon Jul 9 19:12:43 2012 -0700 Use C99 designated initializers in various extension Replies Signed-off-by: Alan Coopersmith Reviewed-by: Keith Packard Tested-by: Daniel Stone Attributes ArcticaProject/nx-libs#382

Lift record to xorg-server-1.4.2 state

2018-02-27T00:49:45+00:00

Lift record to xorg-server-1.2.0/xorg-server-1.3.0.0 state - non-functional changes only

2018-02-27T00:47:50+00:00

Lift record to xorg-server-1.2.0/xorg-server-1.3.0.0 state

2018-02-27T00:44:35+00:00

Lift record to xorg-xserver-7.1/1.1.0 state - non-functional changes only

2018-02-27T00:38:29+00:00

Lift record to xorg-xserver-7.1/1.1.0 state

2018-02-27T00:35:08+00:00

Clearing comments from $XFree86$ (et al.) header lines.

2017-04-19T11:08:45+00:00

record: avoid crash when calling RecordFlushReplyBuffer recursively

2017-04-06T12:09:19+00:00

Backported from X.Org: commit 0801afbd7c2c644c672b37f8463f1a0cbadebd2e Author: Erkki Seppälä Date: Thu Feb 10 15:35:14 2011 +0200 record: avoid crash when calling RecordFlushReplyBuffer recursively RecordFlushReplyBuffer can call itself recursively through WriteClient->CallCallbacks->_CallCallbacks->RecordFlushAllContexts when the recording client's buffer cannot be completely emptied in one WriteClient. When a such a recursion occurs, it will not be broken out of which results in segmentation fault when the stack is exhausted. This patch adds a counter (a flag, really) that guards against this situation, to break out of the recursion. One alternative to this change would be to change _CallCallbacks to check the corresponding counter before the callback loop, but that might affect existing behavior, which may be relied upon. Reviewed-by: Rami Ylimäki Signed-off-by: Erkki Seppälä Signed-off-by: Keith Packard Backported-to-NX-by: Mihai Moldovan Fixes: ArcticaProject/nx-libs#417.

record.c: fix compiler warnings

2017-03-10T18:44:22+00:00

record.c: In function ‘RecordAReply’: record.c:714:7: warning: passing argument 4 of ‘RecordAProtocolElement’ discards ‘const’ qualifier from pointer target type [enabled by default] pri->replyData, pri->dataLenBytes, /* continuation */ -1); ^ record.c:286:1: note: expected ‘void *’ but argument is of type ‘const void *’ RecordAProtocolElement(RecordContextPtr pContext, ClientPtr pClient, ^ record.c:724:10: warning: passing argument 4 of ‘RecordAProtocolElement’ discards ‘const’ qualifier from pointer target type [enabled by default] pri->replyData, pri->dataLenBytes, pri->bytesRemaining); ^ record.c:286:1: note: expected ‘void *’ but argument is of type ‘const void *’ RecordAProtocolElement(RecordContextPtr pContext, ClientPtr pClient, ^ record.c:746:5: warning: passing argument 4 of ‘RecordAProtocolElement’ discards ‘const’ qualifier from pointer target type [enabled by default] pri->dataLenBytes, pri->bytesRemaining); ^ record.c:286:1: note: expected ‘void *’ but argument is of type ‘const void *’ RecordAProtocolElement(RecordContextPtr pContext, ClientPtr pClient, ^