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, 14 Nov 2002 21:15:10 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Serial port problems with cygwin1.dll 1.3.15 on Win98SE Message-ID: <20021115021510.GA16845@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <3.0.6.32.20021114230707.007a23e0@127.0.0.1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3.0.6.32.20021114230707.007a23e0@127.0.0.1> User-Agent: Mutt/1.5.1i On Thu, Nov 14, 2002 at 11:07:07PM +0100, Ton van Overbeek wrote: >Some more input. >Attached strace output from a successfull run with the >cygwin-1.3.14 dll. >What I can spot in the log is that when com4 is read it now >has a read timeout of 1000 (vtime=1000), while in the unsuccessfull >runs vmin was 0. >Does that ring any bells ? Yep. I'm regenerating a snapshot now which may solve this problem. When a ChangeLog shows up with this entry: 2002-11-14 Christopher Faylor * fhandler_serial.cc (fhandler_serial::tcgetattr): Don't take any special action when vmin_ == 0. That will be the snapshot to try. cgf -- 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/