<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.

1 files changed, 1 insertions, 1 deletions

diff --git a/src/eol.c b/src/eol.c
index 3439869..9e80b96 100644
--- a/src/eol.c
+++ b/src/eol.c
@@ -126,7 +126,7 @@ teco_eol_reader_convert(teco_eol_reader_t *ctx, gchar **ret, gsize *data_len, GE
 	}
 	ctx->offset += ctx->block_len;
 
-	if (ctx->offset == ctx->read_len) {
+	if (ctx->offset >= ctx->read_len) {
 		ctx->offset = 0;
 
 		switch (ctx->read_cb(ctx, &ctx->read_len, error)) {