Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 To: cygwin AT cygwin DOT com X-Injected-Via-Gmane: http://gmane.org/ Path: not-for-mail From: Pietro Toniolo Newsgroups: gmane.os.cygwin Subject: Re: Strange behavior of MSVC's printf under cygwin shell? Date: Tue, 26 Mar 2002 09:04:17 +0100 Lines: 10 Message-ID: <3CA02B81.8D679A34@tin.it> References: <4 DOT 3 DOT 1 DOT 2 DOT 20020325164805 DOT 02361a90 AT pop DOT ma DOT ultranet DOT com> NNTP-Posting-Host: 213.140.15.170 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: main.gmane.org 1017129858 12374 213.140.15.170 (26 Mar 2002 08:04:18 GMT) X-Complaints-To: usenet AT main DOT gmane DOT org NNTP-Posting-Date: Tue, 26 Mar 2002 08:04:18 +0000 (UTC) X-Accept-Language: en,it "Larry Hall (RFK Partners, Inc)" wrote: > The problem must be at your end. I don't see it here. Looks like you'll > need to debug it more. Nay, I campiled the proposed program (every package on my side is in the "Last" status) and, with -no-cygwin, I do have an unbuffered stdout. Is it an "undefined behavior" of the c compiler? But why a different default behavior, with and without the flag? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/