This is the mail archive of the
cygwin-developers@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: snapshot-991207
- To: Andrew Dalgleish <andrewd at axonet dot com dot au>
- Subject: Re: snapshot-991207
- From: Chris Faylor <cgf at cygnus dot com>
- Date: Fri, 10 Dec 1999 01:00:42 -0500
- Cc: "'cygwin-developers at sourceware dot cygnus dot com'" <cygwin-developers at sourceware dot cygnus dot com>
- References: <00F8D6E8AB0DD3118F1A006008186C9607C7CE@server1.axonet.com.au>
On Fri, Dec 10, 1999 at 02:54:37PM +1100, Andrew Dalgleish wrote:
>>>>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.
I've checked in changes that should improve this behavior.
>>>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.
>> What shell are you using?
>The shell is bash 2.02 from cygwin b20.1, copied to /bin/sh.exe.
>>
>> Does pwd actually
>> have a value?
>
>What do you mean?
>$(pwd) is a command in a sub-shell, not a variable.
Doh. That's right. I've got make on the brain.
>Shell built-in commands eg $(pwd) never work.
>External commands eg $(dirname /foo/bar) work most times, but hang maybe
>1 time in 20.
>A ^C brings back the prompt every time (but one).
The hanging problem should be fixed.
I think I know how to deal with this problem but it will have to wait
until tomorrow.
cgf