<EC>: fixed insertion of data garbage (invalid reads) and omissions

* This has only ever observed on Win32, probably because the spawning
  behaves very differently.
* The stdout watcher could be invoked even after removing the source,
  so we must be secured against it - this was causing some overflows
  and invalid reads.
* Also, teco_eol_reader_convert() could return 0 even after process
  termination, which would sometimes result in too few bytes being
  inserted.
  This could be provoked relatively easily by invoking ECdir$ repeatedly.

0 files changed, 0 insertions, 0 deletions