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:11:36 -0400
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin-developers AT cygwin DOT com
Subject:	Re: SHOWSTOPPER: [was Re: vfscanf in newlib]
Message-ID:	<20010422201136.A26333@redhat.com>
Reply-To:	cygwin-developers AT cygwin DOT com
Mail-Followup-To:	cygwin-developers AT cygwin DOT com
References:	<EA18B9FA0FE4194AA2B4CDB91F73C0EF08EF0B AT itdomain002 DOT itdomain DOT net DOT au>
Mime-Version:	1.0
User-Agent:	Mutt/1.3.11i
In-Reply-To:	<EA18B9FA0FE4194AA2B4CDB91F73C0EF08EF0B@itdomain002.itdomain.net.au>; from robert.collins@itdomain.com.au on Mon, Apr 23, 2001 at 09:52:51AM +1000

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?

Were you ever able to duplicate the ssh crashing bug?  If not, can
anyone else confirm that this problem has been squashed now?

cgf

- Raw text -