This is the mail archive of the
cygwin-developers@cygwin.com
mailing list for the Cygwin project.
RE: SHOWSTOPPER: [was Re: vfscanf in newlib]
- To: <cygwin-developers at cygwin dot com>
- Subject: RE: SHOWSTOPPER: [was Re: vfscanf in newlib]
- From: "Robert Collins" <robert dot collins at itdomain dot com dot au>
- Date: Mon, 23 Apr 2001 10:09:13 +1000
- Thread-Index: AcDLiORZu/jmcRNDQICWUpbdQWaczAAAJCWg
- Thread-Topic: SHOWSTOPPER: [was Re: vfscanf in newlib]
> -----Original Message-----
> From: Christopher Faylor [mailto:cgf@redhat.com]
> Sent: Monday, April 23, 2001 10:12 AM
> To: cygwin-developers@cygwin.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