From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1897 invoked by alias); 19 Dec 2008 19:35:48 -0000 Received: (qmail 1884 invoked by uid 22791); 19 Dec 2008 19:35:47 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mu-out-0910.google.com (HELO mu-out-0910.google.com) (209.85.134.189) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 19 Dec 2008 19:35:12 +0000 Received: by mu-out-0910.google.com with SMTP id w8so516425mue.8 for ; Fri, 19 Dec 2008 11:35:10 -0800 (PST) Received: by 10.103.214.8 with SMTP id r8mr1371161muq.6.1229715309938; Fri, 19 Dec 2008 11:35:09 -0800 (PST) Received: by 10.103.108.4 with HTTP; Fri, 19 Dec 2008 11:35:09 -0800 (PST) Message-ID: <17393e3e0812191135v64035dfq1e8f25c2a352872@mail.gmail.com> Date: Fri, 19 Dec 2008 19:35:00 -0000 From: "Matt Wozniski" To: cygwin@cygwin.com Subject: Re: printf goes to serial port? In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <494BE168.1020600@rettc.com> X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2008-12/txt/msg00491.txt.bz2 On Fri, Dec 19, 2008 at 2:30 PM, Gary R. Van Sickle wrote: >> From: Alex Martin >> >> Hello, >> >> I have a cygwin environment, running some software I am >> writing to talk to some serial devices. >> >> Somehow, trying to debug why I could not see printf output to >> console, I ran a serial port sniffer and voila all of my >> printf commands are writing on the serial port. >> > > I can't say that it would cross my mind to look for my missing printf output > on a serial port, even if I was using a serial port in other parts of the > program to talk to something. Whatever it was that gave you the hunch to do > that is probably at the core of your problem. My slightly wild guess is that you do an open() on the serial device without a controlling terminal and without passing the O_NOCTTY flag, causing the serial device to become your controlling terminal. ~Matt -- 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/