Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Tue, 07 Jan 2003 16:28:55 -0500 From: Jason Tishler Subject: Re: Cygwin gcc 3.2 seems to break fetchmail In-reply-to: <20030106190025.GA532@tishler.net> To: cygwin AT cygwin DOT com Mail-followup-to: cygwin AT cygwin DOT com Message-id: <20030107212855.GA268@tishler.net> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline User-Agent: Mutt/1.4i References: <20030106190025 DOT GA532 AT tishler DOT net> On Mon, Jan 06, 2003 at 02:00:25PM -0500, Jason Tishler wrote: > Any suggestions on how to best debug this problem or potential root > causes will be greatly appreciated. A friend of mine suggested using -Wall to find questionable fetchmail code that could behave differently under gcc 3.2. The good news is that I quickly found such code. The bad news is that the code is mine! :,( When my original Winsock recv(..., MSG_PEEK) workaround patch: http://sources.redhat.com/ml/cygwin/2002-04/msg01584.html was factored to handle both SSL and non-SSL, I forgot the return statement in the newly created cygwin_read() for the normal code path: http://cygwin.com/ml/cygwin/2002-06/msg00320.html Actually, I am quite amazed that Cygwin fetchmail built with gcc 2.95.x has processed 10,000s of messages without any problems over the last 8+ months. I just uploaded a new fetchmail package to correct this problem. Jason -- PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers Fingerprint: 7A73 1405 7F2B E669 C19D 8784 1AFD E4CC ECF4 8EF6 -- 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/