stdout and stderr are getting mixed up?
sebastian.huber at embedded-brains.de
Thu Jun 22 05:48:47 UTC 2017
On 22/06/17 07:29, Chris Johns wrote:
> On 22/06/2017 15:20, Sebastian Huber wrote:
>> On 22/06/17 07:14, Chris Johns wrote:
>>>> If you need a proper log, then you have to ensure this at application level.
>>> What about this post:
>>> It would imply a line should not be broken up. I do not know.
>> You have thread-local stdio streams in Newlib that use a common output device by
> Is what we do acceptable standard behavior?
I doubt that thread-local stdio streams are in line with POSIX/C.
> The link I posted would suggest otherwise.
It doesn't cite the POSIX standard. I don't know where this atomic
printf() behaviour is defined.
> RTEMS 4.9, 4.10, and 4.11 did not do
> this so is this a regression?
The original post compares the beatnik and pc386 BSPs. It compares an
Epic implementation using the Classic API with one using the POSIX API.
I don't think there is a regression. I remember that the output of
ticker was always mixed up with an interrupt driven console driver.
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.huber at embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
More information about the users