| www.delorie.com/archives/browse.cgi | search |
| Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
| List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
| List-Archive: | <http://sources.redhat.com/ml/cygwin/> |
| List-Post: | <mailto:cygwin AT cygwin DOT com> |
| List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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 |
| Date: | Mon, 13 Jan 2003 13:28:44 -0600 |
| From: | Steve O <bub AT io DOT com> |
| To: | cygwin AT cygwin DOT com |
| Subject: | Re: /dev/tty read is broken! |
| Message-ID: | <20030113132844.A3670@hagbard.io.com> |
| Mime-Version: | 1.0 |
| User-Agent: | Mutt/1.2.5.1i |
John E. A. Wrote: > However if I run the program full speed, or step through the fgetc() on > cygwin without previously typing a character into minicom, then the fgetc() > call hangs. I'm not familiar with the winsup/cygwin/fhandler_serial code, but if I was going to debug this (which sounds like fun, but I don't have the setup), I'd run: strace test > test.dump and see what's happening right before the ^C, then I'd look at the cygwin code mentioned above. -steve -- 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/
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |