Re: printf() stops working after some time

Jeff Johnston <[email protected]>
Newsgroups gmane.comp.lib.newlib
Message-ID <CAOox84urLg=40782n7158cCSoqoXPhQYoh+4Cr07zRrAh9zgdg@mail.gmail.com>
Hi Josef,

Can you provide more details about the original error?  What does perror()
say after the call?
If it is a write error, do you know what the underlying write error is?

Also, what are your configuration options?

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.
.
-- Jeff J.

On Fri, Oct 26, 2018 at 4:27 AM, Josef Wolf <[email protected]> wrote:

> Hallo again,
>
> this thread has drifted to the malloc() issue.
>
> But there are no opinions yet about the primary questions:
>
> > Why are printf/puts inconsisten on the error handling?
> >
> > Is there a way to "auto-clear" this error flag?
> >
> > I have not seen this in older newlib releases.
>
> --
> Josef Wolf
> [email protected]
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.