Experimental Physics and
Industrial Control System

On Apr 9, 2020, at 1:18 PM, Mark Rivers <rivers at cars.uchicago.edu> wrote:

I was going to test the hypothesis that the problem was that stderr needed an fflush after each command.  I was hoping that this would be easy to do from the vxWorks shell, but I'm not sure how to get the FILE  pointer to stderr from the command line?


I want to see if the garbling goes away if I do this in the startup script:


dbLoadTemplate(...)

fflush(stderr)

...


Mark



________________________________
From: J. Lewis Muir <jlmuir at imca-cat.org>
Sent: Thursday, April 9, 2020 1:00 PM
To: EPICS Tech-Talk
Cc: 'Konrad, Martin'; Johnson, Andrew N.; Mark Rivers
Subject: Re: Filtering messages print on the IOC shell console

On 03/27, Mark Rivers wrote:

Hi Martin,

dbLoadTemplate.y is printing messages using fprintf(stderr,...);
My recommendation would be to print all messages to the same stream.

Unfortunately this is out of my control.  The problem I am seeing is the garbling of output from dbLoadTemplate (EPICS base) and the echoing of subsequent vxWorks shell commands (Wind River).

But this suggests that the vxWorks shell is proceeding to execute the next command before the previous one has displayed all of its output on the console?  This does not seem correct.

Any more thoughts on this garbled output issue?  Specifically, how can
it be fixed?

Thanks!

Lewis