Recieved: from Richard DOT Curnow AT st DOT com by popov with local (Exim 3.03 #5)
	id 13qxRO-0005qj-00; Wed, 01 Nov 2000 12:56:30 +0000
Date: Wed, 1 Nov 2000 12:56:30 +0000
From: Richard Curnow <Richard DOT Curnow AT st DOT com>
To: eliz AT is DOT elta DOT co DOT il
Cc: djgpp AT delorie DOT com
Subject: Re: DJGPP Bug Activity
Message-ID: <20001101125629.E7236@bri.st.com>
References: <200011011100 DOT GAA28488 AT delorie DOT com> <Pine DOT SUN DOT 3 DOT 91 DOT 1001101142216 DOT 9403B-100000 AT is>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.4i-nntp
In-Reply-To: <Pine.SUN.3.91.1001101142216.9403B-100000@is>; from eliz@is.elta.co.il on Wed, Nov 01, 2000 at 02:30:24PM +0200
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

On Wed, Nov 01, 2000 at 02:30:24PM +0200, eliz AT is DOT elta DOT co DOT il wrote:
> This was submitted as a bug report to the DJGPP bug-tracking facility 
> (http://www.delorie.com/djgpp/bugs/).
> 
> Please note that controversial reports such as this one, where it's not
> clear whether the bug is in DJGPP or in the target platform, should be
> posted to the DJGPP forum (comp.os.msdos.djgpp) instead of being filed
> with the above site, because most of the time these are not DJGPP bugs. 
> 
> > running on Windows NT 4.0 SP6
> > 
> > This is my test prog (check.c)
> > 
> > #include <stdio.h>
> > #define LT "\n\r"
> > int main () {
> >         printf("Line 5" LT);
> >         printf("Line 4" LT);
> >         printf("Line 3" LT);
> >         printf("Line 2" LT);
> >         printf("Line 1" LT);
> >         fflush(stdout);
> >         return 0;
> > }
> > 
> > In a DOS box I enter
> >   gcc check.c -o check
> > 
> > (With d:\djgpp\bin at the head of the path)
> > 
> > I get two files 'check' and 'check.exe' produced.  If I now type 'check', I
> > get a blank line but no other output.  The same thing happens if LT is
> > changed to either "\n" or "\r\n" as well.
> 
> I cannot reproduce this on NT 4 SP4 and SP5: the program runs as expected,
> producing the 5 lines above.  I don't have access to SP6, though.  Can
> someone who has access to SP6 test this and report the results? 
> 
> My guess would be that this is due to some setup specific to your system 
> (is it possible that 'check' is a name of some command on that machine?).

I've found that if I enter

  check > check.out

  type check.out

I get the expected file contents.  It seems to be a problem which is
specific to file I/O direct to a DOS box.

If the output is fprintf'd to stderr, again nothing appears on the
screen.  If I redirect 2> to a file, the file contains valid output.
Thus, character versus line buffering on output to the DOS box doesn't
seem to be relevant.

For what I want, redirecting to a file and typing that after is a
reasonable work-around, but it would still be nice if direct I/O worked.
However, it's starting to look like it may just be the setup of this PC
rather than a general NT DOS box problem, in which case please cancel
the bug report as a non-problem if no-one else can reproduce it.