public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-no-personal-reply-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Problem with pty allocation code, race condition?
Date: Fri, 21 May 2004 09:14:00 -0000	[thread overview]
Message-ID: <20040521022228.GA31667@coe.bosbc.com> (raw)
In-Reply-To: <Pine.GSO.4.58.0405191755040.17685@slinky.cs.nyu.edu>

On Wed, May 19, 2004 at 06:08:01PM -0400, Igor Pechtchanski wrote:
>On Mon, 17 May 2004, Christopher Faylor wrote:
>
>> On Mon, May 17, 2004 at 09:29:44AM -0400, John P. Rouillard wrote:
>> >Does the last cygwin snapshot contain any code changes in the pty
>> >allocation area?
>>
>> Yes, the very latest snapshot attempts to fix this problem.  Please give
>> it a try and report the results here.
>
>I'm sorry to report that the problem I described in
><http://cygwin.com/ml/cygwin/2004-05/msg00596.html> (multiple xterms
>started in quick succession get the same PTY) still exists in the 20040519
>snapshot.  The output of "ps" after reproducing it with 4 xterms is below,
>if it's of any help (the last bash, PID 1948, is a console).

And, now I finally receive this email...  Amazing.

cgf

--
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/

  reply	other threads:[~2004-05-21  2:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-17 13:35 John P. Rouillard
2004-05-17 14:06 ` Igor Pechtchanski
2004-05-17 16:46 ` Christopher Faylor
2004-05-17 23:43   ` Brian Keener
2004-05-20 10:53   ` Igor Pechtchanski
2004-05-21  9:14     ` Christopher Faylor [this message]
2004-05-25 21:11       ` PLEASE TEST: Latest cygwin snapshot == 1.5.10 alpha Igor Pechtchanski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040521022228.GA31667@coe.bosbc.com \
    --to=cgf-no-personal-reply-please@cygwin.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).