SHOWSTOPPER: [was Re: vfscanf in newlib]
Robert Collins
robert.collins@itdomain.com.au
Sun Apr 22 17:00:00 GMT 2001
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@redhat.com ]
> Sent: Monday, April 23, 2001 9:59 AM
> To: cygwin-developers@cygwin.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 <rbtcollins@hotmail.com>
> >+
> >+ * thread.cc (MTinterface::Init): Always initialise
> per process
> >variables.
> >+
> > Sun Apr 22 19:18:18 2001 Christopher Faylor <cgf@cygnus.com>
> >
> > * 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
>
More information about the Cygwin-developers
mailing list