From:	Clemens Valens <c DOT valens AT mindless DOT com>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Q: fprintf behaviour
Organization:	http://www.remarq.com: The World's Usenet/Discussions Start Here
X-Originating-Host:	195.154.148.69
X-Wren-Trace:	cAIlBRACXiYeTFYgEk5DWUZRQl9dVxROV1xNUFJPQgJcXRdNXRdDQl9XXklaG1EWTRgPARBTJioOH0wPHUcFGUlBDAY=
Message-ID:	<933002162.14440@www.remarq.com>
Lines:	27
Date:	Mon, 26 Jul 1999 07:15:58 -0800
NNTP-Posting-Host:	10.0.3.195
X-Complaints-To:	wrenabuse AT remarq DOT com
X-Trace:	WReNphoon3 933002457 10.0.3.195 (Mon, 26 Jul 1999 08:20:57 PDT)
NNTP-Posting-Date:	Mon, 26 Jul 1999 08:20:57 PDT
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

I use fprintf in an interrupt driven program and it shows
some peculiar behaviour:

The programs sets up and enables interrupt stuff and then
enters the main loop where it processes messages received
from the isr. Every once in a while I make it print some
info to stdout. The bizar thing now is that it doesn't
print anything, until I quit the program. Then it prints
everything it should have printed in the loop. It is like
fprintf is printing to a buffer and only flushes it when
the loop finishes. A 16-bit version of this program does
not have this problem.

When I use a standard printf it does what I expect it to do.

Any suggestions? Is there maybe some mechanism hooked to
the timer interrupt that regularly flushes stdout, which I
might have disabled accidentally? Or is it just another
memory thing?

Thanks in advance,
Clemens



* Sent from RemarQ http://www.remarq.com The Internet's Discussion Network *
The fastest and easiest way to search and participate in Usenet - Free!

- Raw text -