Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Date: Sun, 22 Apr 2001 20:25:23 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-developers AT cygwin DOT com
Cc: cwilson AT ece DOT gatech DOT edu
Subject: Re: SHOWSTOPPER: [was Re: vfscanf in newlib]
Message-ID: <20010422202523.A26689@redhat.com>
Reply-To: cygwin-developers AT cygwin DOT com
Mail-Followup-To: cygwin-developers AT cygwin DOT com, cwilson AT ece DOT gatech DOT edu
References: <EA18B9FA0FE4194AA2B4CDB91F73C0EF08EF0C AT itdomain002 DOT itdomain DOT net DOT au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.11i
In-Reply-To: <EA18B9FA0FE4194AA2B4CDB91F73C0EF08EF0C@itdomain002.itdomain.net.au>; from robert.collins@itdomain.com.au on Mon, Apr 23, 2001 at 10:09:13AM +1000

On Mon, Apr 23, 2001 at 10:09:13AM +1000, Robert Collins wrote:
>> -----Original Message-----
>> From: Christopher Faylor [mailto:cgf AT redhat DOT com]
>> Sent: Monday, April 23, 2001 10:12 AM
>> To: cygwin-developers AT cygwin DOT com
>> Subject: Re: SHOWSTOPPER: [was Re: vfscanf in newlib]
>> 
>> 
>> On Mon, Apr 23, 2001 at 09:52:51AM +1000, Robert Collins wrote:
>> >Committed. The NULL protection should not be needed. if thread_self()
>> >ever returns NULL we are in big trouble across the board. So perhaps
>> >pthread_self should system_printf if it fails ?
>> 
>> Yep.  Or should it be an api_fatal?
>
>as long as cygwin dies horribly when it happens :] Yes api_fatal is
>probably the call. Thanks.
> 
>> Were you ever able to duplicate the ssh crashing bug?  If not, can
>> anyone else confirm that this problem has been squashed now?
>
>I confess to not having an sshd setup to test the bug with. Thus I just
>reviewed the source.

I confess to not understanding how my version of sshd could possibly
have worked, given what I now understand about the problem.

Chuck, could you update to the latest CVS version and let us know if
it fixes the problem that you found.

In the meantime, I have wiped out 1.3.0 from sources.redhat.com.

Since a couple of people seem to be using it, I guess I should bump
the version to 1.3.1.  Sigh.

cgf