Argonne National Laboratory

Experimental Physics and
Industrial Control System

2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017 Index 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017
<== Date ==> <== Thread ==>

Subject: error messages in epics-base (core?)
From: Heinz Junkes <junkes@fhi-berlin.mpg.de>
To: core-talk@aps.anl.gov
Date: Wed, 21 Jun 2017 16:01:04 +0200
Is there a reason why e.g. in src/libCom/log/logClient.c 

at most places 
fprintf (stderr, “ error message …”);
or even 
printf (“ error message “);

is used instead errlogPrintf which uses the errlog-thread (low prio)

This is just one place that I noticed today. I guess this is usually implemented in this way.

But with RTEMS the output on the console is mixed up and not readable anymore.

…
ok 27 - pvt.count (8) == N+1 (8)
ok 28 - Removed 1 listener
# Testing iocLogPrefix
# Listening on port 1026
ok 29 - iocLogInit() == 0
ok 30 - Accepted lnoegw  cclliieenntt:
 ocko n3n1e c-t eCdl iteon tl orge asde rcvoenrf iagtu r"e1d2
7.0.0.1:1026"
ok 32 - prefix matches
...

Heinz


Attachment: smime.p7s
Description: S/MIME cryptographic signature


Replies:
Re: error messages in epics-base (core?) Michael Davidsaver

Navigate by Date:
Prev: Java PvaClientMonitor questions Mark Rivers
Next: Re: error messages in epics-base (core?) Michael Davidsaver
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017
Navigate by Thread:
Prev: Re: Java PvaClientMonitor questions Marty Kraimer
Next: Re: error messages in epics-base (core?) Michael Davidsaver
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017
ANJ, 05 Jul 2017 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·