This is the mail archive of the
newlib@sourceware.org
mailing list for the newlib project.
Re: printf() stops working after some time
Hello,
On Tue, Oct 30, 2018 at 07:09:38PM -0400, Jeff Johnston wrote:
> Can you provide more details about the original error? What does perror()
> say after the call?
perror says "Success". =:-()
> If it is a write error, do you know what the underlying write error is?
write() returns 0, because the rts/cts handshake stopped the serial line and
its output buffer is full.
> Also, what are your configuration options?
--enable-install-libbfd
--enable-languages=c
--with-gnu-ld
--with-gnu-as
--with-newlib
--with-system-zlib
--enable-commonbfdlib
--enable-interwork
--disable-shared
--disable-libssp
--nfp
--gas
--v
--target=m68k-unknown-elf
I use the same set of options to compile binutils, gcc and newlib.
> Looking at the vfprintf.c code, there is no check for the _SERR flag being
> set so it isn't blatantly obvious why this problem is occurring
> for you.
Yes, its somewhat strange. I've not seen this behavior in older newlib
releases.
--
Josef Wolf
jw@raven.inka.de