Mail Archives: cygwin-developers/1999/01/03/12:55:31

From: corinna DOT vinschen AT cityweb DOT de (Corinna Vinschen)
Subject: Strange behaviour with latest snapshot
3 Jan 1999 12:55:31 -0800 :
Message-ID: <>
Mime-Version: 1.0
To: "Christopher G. Faylor" <cgf AT cygnus DOT com>, cygwin32-developers AT cygnus DOT com

Hi Chris,

I have found a strange behaviour, which has already happened
in older snapshots ('til 981126, I believe). Do you remember your
experience with pdksh, that every command begun with the
character `k' instead of the really typed char?

I have now done the following, without changing the sources:

Installed egcs-1.1.1 from Mumits page,
compiled latest newlib snapshot,
compiled libio and libstdc++,
compiled latest winsup snapshot,
compiled tcsh-6.08.00 twice with termcap and ncurses:

starting any of the new compiled tcsh:

> ls
ts: command not found.

Then I took a glimps at the sources of winsup-981230 (
Your code, which did an empty ReadFile() was #if'd 0. I changed the
0 to 1, recompiled it and got in the new compiled tcsh:

> ls
ls		<-- repeated command output
FAQ                ed.term.h          sh.glob.o          tc.os.h
Fixes              ed.term.o          sh.h               tc.os.h.orig

Exiting shell with Ctrl-D didn't work, too. Same behaviour with
new compiled pdksh. But it's strange, that this happens only with
new compiled versions, the previous compiled versions do their job
as expected.

I'm not sure, but I suppose an error in one of the libraries, not
in winsup sources itself, because I have make a test:

I have used the egcs-1.1.1 compiler, latest winsup-981230, but compiled
the shells with the older libraries from last dev-src package, built with
egcs-1.1b and one of the previous winsup-snapshots (981201, I guess).
This works fine, again.

Is it possible, that there's an error in the latest newlib???


- Raw text -

  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019