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: Fri, 30 Jul 2004 12:14:54 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: text/binmode endless loop Message-ID: <20040730101454.GC1762@cygbert.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20040729232510.GA19261@trixie.casa.cgf.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i On Jul 30 09:33, Alexander Gottwald wrote: > Christopher Faylor wrote: > > > > This shows write() being called repeatedly. The fact that > > setmode_helper shows up a bunch of time doesn't mean that it is caught > > in a loop. You can't infer that from strace. You'd need to confirm > > that with gdb. > > But why does it change repeatedly from text to bin and back to text? That's a good question. The output is generated by calls to the setmode function. Since setmode isn't called from inside Cygwin, it must be called from the application. It looks like a race but actually that's something you will have to debug. Concentrate on calls to getmode and setmode for the beginning. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Co-Project Leader mailto:cygwin@cygwin.com Red Hat, Inc. -- 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/