X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.3 required=5.0 	tests=AWL,BAYES_00
X-Spam-Check-By: sourceware.org
Message-ID: <494C01A8.8040200@rettc.com>
Date: Fri, 19 Dec 2008 13:18:48 -0700
From: Alex Martin <alex AT rettc DOT com>
User-Agent: Thunderbird 2.0.0.18 (Windows/20081105)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: printf goes to serial port?
References: <494BE168 DOT 1020600 AT rettc DOT com> <E464473DC145404FBD632475DDAF55C6 AT DFW5RB41>
In-Reply-To: <E464473DC145404FBD632475DDAF55C6@DFW5RB41>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

Well, I was using a port monitor to debug some of the traffic between my 
serial device, and my software, when I noticed the output accidentally.

I am not sure when the behavior started. It used to work fine, I was 
using printf to debug things, then I turned off all of those printf 
statements, and continued development on the gui side (fox toolkit) of 
my application, and then had to go in and modify my low level serial 
class and was trying to get my printf debug output again, to no avail.

I have updated cygwin a few times, otherwise I cannot think of anything 
specific.

What other details can I provide?

Alex Martin

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.
> 
>> 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
>>
> 

--
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/