stdout and stderr are getting mixed up?
jameszxj at gmail.com
Fri Jul 7 08:38:41 UTC 2017
I test on my xilinx z7020 board, system reboot after rtems_bsdnet_initialize_network() returns success and a
message "RTEMS bsdnet_initialize_network returned OK" print out.
I tried to add another printf("...") after it, no more message print out.
The previous RSB version is OK, except mixed messages.
------------------ Original ------------------
From: "Chris Johns";<chrisj at rtems.org>;
Date: Thu, Jul 6, 2017 03:06 PM
To: "Sebastian Huber"<sebastian.huber at embedded-brains.de>; "Heinz Junkes"<junkes at fhi-berlin.mpg.de>; "rtems-users at rtems.org"<users at rtems.org>;
Subject: Re: stdout and stderr are getting mixed up?
On 06/07/2017 15:11, Sebastian Huber wrote:
> On 06/07/17 03:29, Chris Johns wrote:
>> I am seeing the same issue when starting the shell while overlapping output is
>> happening on stdout and stderr when stderr has been redirected (using
>> libmisc/redirector). I am yet to look into this and I suspect this will not
>> happen for a while. It could be related to the zynq's polled console driver, I
>> do not know.
> Since the mixed output from stderr and stdout is observed on Mac OS, Linux and
> FreeBSD as well I don't think we have to change anything here for RTEMS.
I tend to agree, I just need to check and make sure this is the reason.
users mailing list
users at rtems.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the users