On 03/26, J. Lewis Muir wrote:
> On 03/26, Johnson, Andrew N. via Tech-talk wrote:
> > The only place IOC code should be using printf() or fprintf(stderr,
> > …) is when reporting errors from initialization commands that were
> > run in a startup script or from the command-line (those should not
> > use errlog() because the output gets out of sync since it has to pass
> > through the logging system before being printed).
>
> A problem I often see on VxWorks VME crate IOC consoles is that output
> is corrupted. It looks as if two or more threads or processes are
> writing to the console at the same time. Does your suggestion about
> where you consider it appropriate to use printf and fprintf include this
> situation? How can this be avoided?
Hi, Andrew!
Any thoughts on this?
Thanks!
Lewis
- References:
- Filtering messages print on the IOC shell console Paduan Donadio, Marcio via Tech-talk
- Re: Filtering messages print on the IOC shell console Johnson, Andrew N. via Tech-talk
- Re: Filtering messages print on the IOC shell console J. Lewis Muir via Tech-talk
- Navigate by Date:
- Prev:
RE: NTNDArray array filter does not work on value Mark Rivers via Tech-talk
- Next:
Re: EPICS7 roller-coaster Michael Davidsaver via Tech-talk
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
<2020>
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: Filtering messages print on the IOC shell console J. Lewis Muir via Tech-talk
- Next:
Re: Filtering messages print on the IOC shell console Konrad, Martin via Tech-talk
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
<2020>
2021
2022
2023
2024
|