This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Socket read problem on Windows XP Pro & Cygwin
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/