X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 	tests=AWL,BAYES_00
X-Spam-Check-By: sourceware.org
Message-ID: <494C0B68.1040207@rettc.com>
Date: Fri, 19 Dec 2008 14:00:24 -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> <494C01A8 DOT 8040200 AT rettc DOT com> <AE8B53D1324D471B8AAE848A5A215E45 AT DFW5RB41>
In-Reply-To: <AE8B53D1324D471B8AAE848A5A215E45@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



Gary R. Van Sickle wrote:
>> From:  Alex Martin
>>
>> 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?
>>
> 
> Well, whatever details you have.  I'm still in "pull mode" here, which isn't
> conducive to problem-solving.  So far I've been able to gather:
> 
> 1.  You are developing some sort of app that communicates over a serial port
> to some other device.
> 2.  You "have a cygwin environment".
> 3.  The app has a GUI, using something called "fox toolkit" (with which I am
> not familiar).
> 4.  You had debug printf()s that used to work, then a bunch of stuff
> changed, and now they work differently.
> 
> A few gaps that need filling before anything better than SWAGs can come your
> way:
> - Is this app a Cygwin app, 

No, it is a windows app.

I am using cygwin primarily because I get the /dev/ttyS* devices. I 
could not find info on how to talk to a serial port in the windows world 
without using "MFC" which I refuse to touch.

or is Cygwin involved only perhiperally (e.g.
> you're using Cygwin make to run the MinGW toolchain), 

No mingw. Using all of cygwin's make, g++, etc.

or is Cygwin not
> directly involved at all and you're saying "My non-Cygwin-related app was
> working fine, I changed a bunch of stuff in the app and also upgraded
> Cygwin, and now the app is broke and I'm thinking Cygwin could be to blame"?

I do not think the app is broken. Somehow stdout is going to the serial 
port, my code relating to file descriptors (a serialio class that 
provides functions like open, close, read, write, flush), opening and 
closing the devices, etc has never changed (that is, the code is the 
same code since back when printf worked). Other code has changed, that 
is, the gui layout, function flow, etc.

> - Since your app is a GUI app, where did you expect your printf()s to go?

Well, someone taught me to use cygwin in this manner, and I have been 
doing so for a long time, that is, I can use a cygwin window to invoke 
my windows app, and the cygwin console would catch printfs (stdout 
chatter), so you can use it as a debug console.

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