Mailing-List:	contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-developers-subscribe AT sourceware DOT cygnus DOT com>
List-Archive:	<http://sourceware.cygnus.com/ml/cygwin-developers/>
List-Post:	<mailto:cygwin-developers AT sourceware DOT cygnus DOT com>
List-Help:	<mailto:cygwin-developers-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender:	cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin-developers AT sourceware DOT cygnus DOT com
Message-ID:	<00F8D6E8AB0DD3118F1A006008186C9607C7CD@server1.axonet.com.au>
From:	Andrew Dalgleish <andrewd AT axonet DOT com DOT au>
To:	"'cygwin-developers AT sourceware DOT cygnus DOT com'"
	<cygwin-developers AT sourceware DOT cygnus DOT com>
Subject:	RE: snapshot-991207
Date:	Fri, 10 Dec 1999 12:58:02 +1100
X-Priority:	3
MIME-Version:	1.0
X-Mailer:	Internet Mail Service (5.0.1458.49)

> Nope.  I've duplicated it.  I'll see what the problem is.  It doesn't
> seem to be thread-safe related and it probably isn't even a problem
> with
> the new signal code.  It looks like my new mutex-like object is not as
> robust as I thought.
> 
[Andrew Dalgleish]  

This might be related - "echo $(pwd)" outputs just a newline.
I first observed this in winsup-19991205, but I have not even begun to
look.
This was built on NT4sp5 + cygwin B20.1 + Mumit's gcc 2.95 +
winsup-19991204.


BTW, winsup/Makefile refers to /bin/true, but that's not where mine was
('tis now).
Should we try to follow the FHS where possible?

Cheers

- Raw text -