Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Sun, 16 Sep 2001 10:14:11 +0200 From: Harry Kuiper To: cygwin AT cygwin DOT com Subject: Re: ftp segfaults on startup with cygwin-1.3.3-2 Message-ID: <20010916101411.B633@mumon.coopernet> Mail-Followup-To: cygwin AT cygwin DOT com References: <20010914114632 DOT F32343 AT redhat DOT com> <20010915220407 DOT A596 AT mumon DOT coopernet> <20010915172758 DOT L28425 AT redhat DOT com> <20010916022337 DOT A633 AT mumon DOT coopernet> <20010915220917 DOT C29496 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.15i In-Reply-To: <20010915220917.C29496@redhat.com>; from cgf@redhat.com on Sat, Sep 15, 2001 at 10:09:17PM -0400 On Sat, Sep 15, 2001 at 10:09:17PM -0400, Christopher Faylor wrote: > On Sun, Sep 16, 2001 at 02:23:37AM +0200, Harry Kuiper wrote: > >On Sat, Sep 15, 2001 at 05:27:58PM -0400, Christopher Faylor wrote: > >> On Sat, Sep 15, 2001 at 10:04:07PM +0200, Harry Kuiper wrote: > >> >On Fri, Sep 14, 2001 at 11:46:32AM -0400, Christopher Faylor wrote: > >> >> On Thu, Sep 13, 2001 at 08:07:55AM -0500, Chris Green wrote: > >> >> >Of course, I should have sent you this: it's the output of cygcheck -v -s > >> >> > >> >> This problem should be fixed in the 2001-Sep-14 snapshot. > >> > > >> >Sorry, on my system (win95) still all network related stuff crashes > >> >with same stacktrace as before. > >> > >> If it is the *same* stacktrace as before then you haven't actually > >> updated your cygwin1.dll. The numbers would be different if you > >> had. > > > >The numbers are different I'm afraid. Just to make sure I did not make a > >mistake: I installed package cygwin-inst-20010914.tar.bz2. > > If you upgrade your Windows 95 box to a later version of Winsock (possibly > upgrading Internet Explorer will do this) the problem should go away. Ok... In that case I'll have to stick to cygwin-1.3.2 for the time being. You see this is a machine I use for work and I'm not allowed to upgrade it. We lose too many working hours (days really) upgrading otherwise stable windoze boxes to "fix" some small problem only to find that the upgrade triggers all kinds of new problems. BTW are you sure it is Winsock? I mean, ssh does work with cygwin-1.3.3 and I suppose it uses Winsock as well. Another possibility could be the problen is in inetutils as it contains ftp, telnet, rlogin and rsh but not ssh. -- Harry Kuiper hkuiper AT xs4all DOT nl Haarlem, The Netherlands hkuiper AT quicknet DOT nl harry DOT kuiper AT ict DOT nl (work) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/