Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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 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: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: ; 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