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 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: SHOWSTOPPER: [was Re: vfscanf in newlib] X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0 content-class: urn:content-classes:message Date: Mon, 23 Apr 2001 10:09:13 +1000 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: SHOWSTOPPER: [was Re: vfscanf in newlib] Thread-Index: AcDLiORZu/jmcRNDQICWUpbdQWaczAAAJCWg From: "Robert Collins" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id UAA28721 > -----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. > > cgf > Rob