Bug#323994: Please close: works in etch

[Peter Moulder <Peter.Moulder@infotech.monash.edu.au>]

The versions of xterm, libxt6 etc. currently in testing do not exhibit
this overlapping memcpy regions bug.

(Incidentally, this bug was wrongly reassigned from xlibs to xkb-data:
it should have gone to libxt6 if anywhere.)

Tested with:

  xterm      222-1etch2 and 224-1
  libxt6     1.0.2-2
  valgrind   3.2.1-1

on a machine that (for the most part) tracks testing.


[valgrind does still give a warning about close(-1) and a write from
 uninitialized data, though it gives no backtrace for the first, and the
 backtrace for the second seems incorrect, even when compiled with -g -O0.]


pjrm.