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: Christopher Faylor <cgf at redhat dot com>
- Date: Sun, 22 Apr 2001 20:25:23 -0400
- Cc: cwilson at ece dot gatech dot edu
- References: <EA18B9FA0FE4194AA2B4CDB91F73C0EF08EF0C@itdomain002.itdomain.net.au>
- Reply-To: cygwin-developers at cygwin dot com
On Mon, Apr 23, 2001 at 10:09:13AM +1000, Robert Collins wrote:
>> -----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.
I confess to not understanding how my version of sshd could possibly
have worked, given what I now understand about the problem.
Chuck, could you update to the latest CVS version and let us know if
it fixes the problem that you found.
In the meantime, I have wiped out 1.3.0 from sources.redhat.com.
Since a couple of people seem to be using it, I guess I should bump
the version to 1.3.1. Sigh.
cgf