Mail Archives: cygwin/2004/04/07/11:27:07
Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
Sent by: cygwin-owner AT cygwin DOT com
04/07/2004 04:07 AM
Please respond to cygwin
To: Cygwin List <cygwin AT cygwin DOT com>
cc:
Subject: Re: Cygwin1.dll problem with Hyperthreaded
machines.
On Apr 6 18:29, Chuck McDevitt wrote:
> I upgraded, and it didn't help.
What about the latest developers snapshot from
http://http://www.cygwin.com/snapshots/ ?
Corinna
--
Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
Sent by: cygwin-owner AT cygwin DOT com
04/07/2004 04:07 AM
Please respond to cygwin
To: Cygwin List <cygwin AT cygwin DOT com>
cc:
Subject: Re: Cygwin1.dll problem with Hyperthreaded
machines.
On Apr 6 18:29, Chuck McDevitt wrote:
> I upgraded, and it didn't help.
What about the latest developers snapshot from
http://http://www.cygwin.com/snapshots/ ?
Corinna
-----------------------------
Ok, I upgraded to the latest snapshot. This did change the symptoms. I
no longer see the thread message.
But, under pd ksh:
CMCDEVITT> test.ksh
Test Failed......Path is empty
Test ended.
CMCDEVITT> test.ksh
Memory fault (core dumped)
CMCDEVITT> test.ksh
Test Failed......Path is empty
Test ended.
CMCDEVITT> test.ksh
Test Failed......Path is empty
Test ended.
CMCDEVITT> test.ksh
Memory fault (core dumped)
Under bash, the symptoms are different... I don't get the "test failed"
problem, and don't get core dumps,
but bash will hang, leaving the shell unresponsive to ctrl-c, and not
using any CPU... The only way to stop it is to kill the process.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -