public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Gary R. Van Sickle" <g.r.vansickle@att.net>
To: <cygwin@cygwin.com>
Subject: RE: printf goes to serial port?
Date: Fri, 19 Dec 2008 19:31:00 -0000	[thread overview]
Message-ID: <E464473DC145404FBD632475DDAF55C6@DFW5RB41> (raw)
In-Reply-To: <494BE168.1020600@rettc.com>

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

  reply	other threads:[~2008-12-19 19:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-19 18:02 Alex Martin
2008-12-19 19:31 ` Gary R. Van Sickle [this message]
2008-12-19 19:35   ` Matt Wozniski
2008-12-19 20:35     ` Alex Martin
2008-12-19 20:19   ` Alex Martin
2008-12-19 20:38     ` Gary R. Van Sickle
2008-12-19 21:01       ` Alex Martin
2008-12-19 21:23         ` Gary R. Van Sickle
2008-12-19 21:32         ` Larry Hall (Cygwin)
2009-01-04 19:22 Bob van Loosen
2009-01-04 21:30 ` Dave Korn
2009-01-04 21:45   ` Bob van Loosen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E464473DC145404FBD632475DDAF55C6@DFW5RB41 \
    --to=g.r.vansickle@att.net \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).