On 5 April 2009 00:03, Christopher Faylor wrote:
> On Sat, Apr 04, 2009 at 03:11:06PM -0700, Josh Stone wrote:
>>I've discovered a deadlock in Cygwin which is pretty easy to
>>reproduce.?? This seems to happen on all of the console windows I can
>>find, except for running in a normal cmd.exe. All
of the tty layer to get right.
>
Hi cgf, thanks for the update. Do you have a bugzilla that I can use to
track this?
Josh
--
View this message in context:
http://www.nabble.com/TTY-write-deadlock-tp22888321p23118994.html
Sent from the Cygwin list mailing list archive at Nabble.com.
--
Unsu
On Sat, Apr 04, 2009 at 08:03:48PM -0400, Christopher Faylor wrote:
>On Sat, Apr 04, 2009 at 03:11:06PM -0700, Josh Stone wrote:
>>I've discovered a deadlock in Cygwin which is pretty easy to
>>reproduce.?? This seems to happen on all of the console windows I can
>>find, except for running in a nor
On Sat, Apr 04, 2009 at 03:11:06PM -0700, Josh Stone wrote:
>Hi,
>
>I've discovered a deadlock in Cygwin which is pretty easy to
>reproduce.?? This seems to happen on all of the console windows I can
>find, except for running in a normal cmd.exe. All of these are
>affected though: xterm, rxvt, min
Hi,
I've discovered a deadlock in Cygwin which is pretty easy to
reproduce. This seems to happen on all of the console windows I can
find, except for running in a normal cmd.exe. All of these are
affected though: xterm, rxvt, mintty, puttycyg+cthelper, and putty
localhost -> cygwin sshd.
To rep
5 matches
Mail list logo