Subject: |
errlogPrintf in OSD implementation |
From: |
"Jun-ichi Odagiri" <[email protected]> |
To: |
"'EPICS Tech-Talk'" <[email protected]> |
Date: |
Thu, 12 May 2005 10:14:01 +0900 |
Hi all,
We are implementing OSD-library of ITRON referring to the existing ones,
such as RTEMS, VxWorks and so forth.
In those libraries, errlogPrintf is used to print out error messages from
epicsThread, epicsEvent and epicsSignal.
On the other hand, APIs in those facilities are used to implement
errlogPrintf itself.
So, a trivial bug in the library under construction caused a loop of
recursive call like:
epicsSignal ->
errlogPrintf ->
epicsSignal ->
errlogPrintf ->
......
Though it might not happen once the OSD-library will have been
well-debugged, I guess it would be better not to use errlogPrintf in the
OSDs which are used to implement errlogPrintf itself.
Could anyone have advice or comments on this?
Thanks a lot in advance.
J. Odagiri
High Energy Accelerator Research Organization (KEK),
Oho 1-1, Tsukuba, Japan
- Replies:
- RE: errlogPrintf in OSD implementation Jeff Hill
- Navigate by Date:
- Prev:
RE: excessive ioc memory utilization Jeff Hill
- Next:
RE: errlogPrintf in OSD implementation Jeff Hill
- 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: excessive ioc memory utilization Jeff Hill
- Next:
RE: errlogPrintf in OSD implementation Jeff Hill
- 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
|