xserver-multidpi/xkb
Keith Packard 9ff7ff2fda Fix MEMORY SMASH in XkbCopyKeymap.
XkbCopyKeymap reallocates the destination keymap when it is not large enough
to hold the source data. When reallocating the map->types data, it needs to
zero out the new entries. The computation for where to start bzero'ing was
accounting for the size of the data type twice, once implicitly in the
pointer arithmetic, and once explicitly with '* sizeof (XkbKeyTypeRec)'.
This would often lead to random memory corruption when the destination
keymap had existing map->types data.
2007-07-04 23:38:27 -07:00
..
ddxBeep.c
ddxCtrls.c
ddxDevBtn.c
ddxFakeBtn.c
ddxFakeMtn.c
ddxInit.c
ddxKeyClick.c
ddxKillSrv.c
ddxLEDs.c
ddxList.c
ddxLoad.c
ddxPrivate.c
ddxVT.c
Makefile.am
maprules.c
README.compiled
xkb.c
xkb.h
xkbAccessX.c
xkbActions.c
XKBAlloc.c
xkbDflts.h
xkberrs.c
xkbEvents.c
xkbfmisc.c
XKBGAlloc.c
xkbInit.c
xkbLEDs.c
XKBMAlloc.c
XKBMisc.c
xkbout.c
xkbPrKeyEv.c
xkbPrOtherEv.c
xkbSwap.c
xkbtext.c
xkbUtils.c Fix MEMORY SMASH in XkbCopyKeymap. 2007-07-04 23:38:27 -07:00
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.