public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Geoffrey Noer <noer@cygnus.com>
To: rwilson@cfawilson.harvard.edu (Bob Wilson)
Cc: gnu-win32@cygnus.com
Subject: Re: Opening COM2
Date: Mon, 07 Apr 1997 15:27:00 -0000	[thread overview]
Message-ID: <199704072159.OAA16472@cirdan.cygnus.com> (raw)
In-Reply-To: <199704032002.PAA00930@cfawilson.harvard.edu>

Bob Wilson wrote:
> 
> I have a program which ran correctly when compiled on a gnu-win32
> package from about a year ago, but is failing when compiled with 17.1
> beta.  The machine is running NT 3.51 and COM2 is connected to a
> microprocessor with only td, rd and ground connected.  The open:
> 
>         if ((comfd = open("com2", O_RDWR | O_TEXT)) <= 0) {
>             fprintf(stderr, "Cmd: Unable to open terminal\n");
>             exit(1);
>         }
> 
> hangs.

This should be fixed in beta 18.  I encountered similar problems trying to
talk to a serial port in a cygwin32-based gdb a little while ago.  The
solution was to rewrite some of the fhandler.cc code in the cygwin.dll
such that the classes make a little more sense.

The bottom line is that fhandler_base::open should not be checking
symlink/executable status of files, instead that code should be in
fhandler_disk_file::open which also does everything that
fhandler_base::open does.  Opening a com port is a fhandler_tty::open which
just defaults to the fhandler_base::open behavior.  This did the trick
for me.

-- 
Geoffrey Noer
noer@cygnus.com
-
For help on using this list, send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

  parent reply	other threads:[~1997-04-07 15:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-04-03 13:20 Bob Wilson
1997-04-03 22:44 ` Jim Balter
1997-04-03 23:05 ` Fergus Henderson
1997-04-07 15:27 ` Geoffrey Noer [this message]
1997-04-07  8:52 David Fiddes
1997-05-14 22:52 Markus Maeder
1997-05-15 14:19 Gary Liddle
1997-05-15 23:48 Markus Maeder

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=199704072159.OAA16472@cirdan.cygnus.com \
    --to=noer@cygnus.com \
    --cc=gnu-win32@cygnus.com \
    --cc=rwilson@cfawilson.harvard.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).