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 09:52:51 +1000 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: SHOWSTOPPER: [was Re: vfscanf in newlib] Thread-Index: AcDLhxbfWuK/u6OOQIusALx9vk1j8wAAB0wg From: "Robert Collins" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id UAA28151 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 ? Rob > -----Original Message----- > From: Christopher Faylor [mailto:cgf AT redhat DOT com] > Sent: Monday, April 23, 2001 9:59 AM > To: cygwin-developers AT cygwin DOT com > Subject: Re: SHOWSTOPPER: [was Re: vfscanf in newlib] > > > On Mon, Apr 23, 2001 at 09:29:19AM +1000, Robert Collins wrote: > >Ok if I check this in? > > > >Index: ChangeLog > >=================================================================== > >RCS file: /cvs/src/src/winsup/cygwin/ChangeLog,v > >retrieving revision 1.657 > >diff -u -p -r1.657 ChangeLog > >--- ChangeLog 2001/04/22 23:18:27 1.657 > >+++ ChangeLog 2001/04/22 23:36:31 > >@@ -1,3 +1,7 @@ > >+Mon Apr 23 9:27:00 2001 Robert Collins > >+ > >+ * thread.cc (MTinterface::Init): Always initialise > per process > >variables. > >+ > > Sun Apr 22 19:18:18 2001 Christopher Faylor > > > > * features.h: Reinstate as wrapper for sys/features.h. > > Yup. > > Do you think this will solve the sshd core dumping problem? Do we > need the NULL protection that Corinna proposed, too? > > cgf >