Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Thu, 22 Jan 2004 09:23:01 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: fetchmail problem with latest cygwin-1.5.6-1 Message-ID: <20040122142301.GE29228@redhat.com> Mail-Followup-To: cygwin@cygwin.com References: <20040121144236.GD1920@tishler.net> <87ektsnz6s.fsf@vzell-de.de.oracle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87ektsnz6s.fsf@vzell-de.de.oracle.com> User-Agent: Mutt/1.4.1i X-IsSubscribed: yes Reply-To: cygwin@cygwin.com On Thu, Jan 22, 2004 at 09:51:39AM +0100, Dr. Volker Zell wrote: >>>>>> "Jason" == Jason Tishler writes: > > Jason> Volker, > Jason> On Mon, Jan 19, 2004 at 08:00:54PM +0100, Dr. Volker Zell wrote: > >> fetchmail doesn't work with the latest cygwin-1.5.6-1. See below: > >> > >> fetchmail: reading message Dr.Volker.Zell@bigip-amerimap.oraclecorp.com:207 of 213 (3253 header octets) fetchmail: (10881 body octets) > >> 691 [main] sh 940 sig_send: error sending signal -33 to pid 940, pipe handle 0x324, Win32 error 232 > >> 51772 [main] sh 940 sig_send: error sending signal -33 to pid 940, pipe handle 0x324, Win32 error 232 > >> fetchmail: not flushed > >> fetchmail: reading message Dr.Volker.Zell@bigip-amerimap.oraclecorp.com:208 of 213 (3204 header octets) > >> 125 [main] fetchmail 2200 fhandler_base::dup: dup(/dev/null) failed, handle 1C0, Win32 error 6 > > Jason> FWIW, I cannot reproduce the above problem on Windows 2000 SP4 under > Jason> cygwin-1.5.6-1 or the 2004-Jan-21 snapshot. BTW, my fetchmail and > Jason> procmail setups appear to be similar to yours. > >Well I cannot produce the problem either on a W2K server edition at >home, which is otherwise setup exactly as my laptop on w2k prof. edition. > >I just noticed that on my laptop fetchmail runs fine when running under >gdb. > >So how can I debug this. Do I need a debuggable cygwin dll ? Yes. And, building with --enable-debugging might be useful since there is a chance that it will detect handle corruption which, I suspect is what is going wrong. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/