Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Wed, 31 Oct 2001 21:28:06 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: pthread: thread switching bug?
Message-ID: <20011031212806.A30033@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <3BCCB65E DOT 77D66FE2 AT hszk DOT bme DOT hu> <20011016203656 DOT A30680 AT redhat DOT com> <1003665677 DOT 2183 DOT 50 DOT camel AT lifelesswks> <3BD72CC1 DOT B2BF80D7 AT hszk DOT bme DOT hu> <1004571833 DOT 1701 DOT 165 DOT camel AT lifelesswks>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1004571833.1701.165.camel@lifelesswks>
User-Agent: Mutt/1.3.21i

On Thu, Nov 01, 2001 at 10:43:52AM +1100, Robert Collins wrote:
>On Thu, 2001-10-25 at 07:04, Nemeth Marton wrote:
>t.
>> > 
>> > Can you see whether you can reproduce the behaviour when writing to a
>> > file, not to stdout? (If you are not using fprintf now, start by trying
>> > with fprintf (stdout,...)). Let me know via the list whether you can
>> > make this happen with a standard file/console with fprintf and we'll
>> > take it from there,
>> > 
>> > Rob
>> 
>> I've checked the fallowing:
>> 
>>                     | without redirection | with shell redirection to
>> file
>>                     |                     | ">testfile.txt"
>> --------------------|---------------------|---------------------------------
>> printf(...)         | bug exist           | bug does not exist
>> --------------------|---------------------|---------------------------------
>> fprintf(stdout, ...)| bug exist           | bug does not exist
>> --------------------|---------------------|---------------------------------
>> 
>>         NMarci
>> 
>> P.S. It seems that I couldn't post messages to cygwin AT cygwin DOT com, that's
>> why I do a CC also.
>
>If you are behind a blocked mail server, you need to be subscribed to
>post messages. That is documented in the bounce message AFAIK.

Yes, in the usual strange syncronicity that amazes and confounds us all,
this week's cause for consternation is the inability to send email to
cygwin AT cygwin DOT com.  There are a few people who are puzzled by the
bounce messages.  I think this mainly owes to the fact that they are
not actually reading the bounce messages.

>Thanks for the testing, you've shown that there is non thread safe code,
>probably in the fhandler_consoler in cygwin, or possibly in the MS
>Windows console code. Right now we don't know which.

I'm still not sure why this is a cygwin bug.  Is there some requirement
that writes to the console be atomic?  Your (Robert's) original email
indicated that the Opengroup spec didn't have this as a requirement.

I'm sure that output to files is different than output to consoles
but I"m not sure that is a bug.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/