Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <435AAAB9.27CDE133@dessent.net>
Date: Sat, 22 Oct 2005 14:10:17 -0700
From: Brian Dessent <brian AT dessent DOT net>
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Socket read problem on Windows XP Pro & Cygwin
References: <20051022035348.RADA2767.eastrmmtao03.cox.net@[172.18.52.8]> <4359C50C DOT 76649CA1 AT dessent DOT net> <loom DOT 20051022T083200-857 AT post DOT gmane DOT org> <4359EB14 DOT E677A317 AT dessent DOT net> <loom DOT 20051022T153140-747 AT post DOT gmane DOT org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com

Todd Rearick wrote:

> > > #define OUTPUT_DEVICE   "COM4"
> >
> > *cough*
> 
> Like I said.  I'm not having a problem with output.  The program fails even
> when I run it with the options "-x -d"....in this case, COM4 is never even
> opened..and no attempts are made to write to it.  All the program does in this
> case is read from the socket and print the data out to STDOUT....and THAT
> doesn't even work.  The read never returns any data to me....

What I was trying to emphasize is that passing "COM4" to open() in a
Cygwin program sets you up for a world of hurt, unless you understand
precisely what you're doing.  It may not matter now, but if you do
anything non-trivial with the port, it will.

Brian

--
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/