X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00 X-Spam-Check-By: sourceware.org From: "Gary R. Van Sickle" To: References: <494BE168 DOT 1020600 AT rettc DOT com> Subject: RE: printf goes to serial port? Date: Fri, 19 Dec 2008 13:30:45 -0600 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: <494BE168.1020600@rettc.com> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Note-from-DJ: This may be spam > 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. > Any idea how to fix this? > Well, no, not really, since you've given very few details to go on. I'd SWAG that you've somewhere, somehow, redirected stdout to the serial port you're trying to talk to those devices on. > Thanks, > Alex Martin > -- Gary R. Van Sickle -- 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/