xserver/xkb
Julien Cristau a2d6932ad4 xkb: don't call atoi(NULL) when parsing argv
If the -ardelay or -arinterval options have no argument, there's no
point trying to read it.

See
http://www.forallsecure.com/bug-reports/feb3db57fc206d8df22ca53a6907f74973876272/

Reported-by: Alexandre Rebert <alexandre@cmu.edu>
Signed-off-by: Julien Cristau <jcristau@debian.org>
Reviewed-by: Alan Coopersmith <alan.coopersmith@oracle.com>
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2013-07-02 15:12:29 +10:00
..
Makefile.am
README.compiled
XKBAlloc.c
XKBGAlloc.c
XKBMAlloc.c
XKBMisc.c
XKM_file_format.txt
ddxBeep.c
ddxCtrls.c
ddxKillSrv.c
ddxLEDs.c
ddxLoad.c
ddxPrivate.c
ddxVT.c
maprules.c
xkb.c
xkb.h
xkbAccessX.c
xkbActions.c xkb: Fixes to LatchMods/LatchGroup 2013-03-06 11:22:38 +10:00
xkbDflts.h
xkbEvents.c
xkbInit.c xkb: don't call atoi(NULL) when parsing argv 2013-07-02 15:12:29 +10:00
xkbLEDs.c
xkbPrKeyEv.c
xkbSwap.c
xkbUtils.c
xkbfmisc.c
xkbgeom.h
xkbout.c
xkbtext.c
xkmread.c

The X server uses this directory to store the compiled version of the
current keymap and/or any scratch keymaps used by clients.  The X server
or some other tool might destroy or replace the files in this directory,
so it is not a safe place to store compiled keymaps for long periods of
time.  The default keymap for any server is usually stored in:
     X<num>-default.xkm
where <num> is the display number of the server in question, which makes
it possible for several servers *on the same host* to share the same 
directory.

Unless the X server is modified, sharing this directory between servers on
different hosts could cause problems.