Hi Till,
Thanks for the explanation, that helped a lot, I'll make the changes.
Has anybody ever seen any of these error messages generated:
pthread_mutex_lock returned EINTR. Violates SUSv3
pthread_cond_timedwait returned EINTR. Violates SUSv3
pthread_cond_wait returned EINTR. Violates SUSv3
I'm considering removing the internal routines that check for and print those
in the 3.15 series since I've never seen them myself or any reports of them on
tech-talk, and I suspect none of our current OSs would return EINTR from those
routines.
- Andrew
--
If a man is offered a fact which goes against his instincts, he will
scrutinize it closely, and unless the evidence is overwhelming, he will
refuse to believe it. If, on the other hand, he is offered something
which affords a reason for acting in accordance to his instincts, he
will accept it even on the slightest evidence. -- Bertrand Russell
- Replies:
- Re: epicsEvent (posix implementation) bug ? Eric Norum
- References:
- epicsEvent (posix implementation) bug ? Till Straumann
- Re: epicsEvent (posix implementation) bug ? Andrew Johnson
- Re: epicsEvent (posix implementation) bug ? Till Straumann
- Navigate by Date:
- Prev:
Re: ca_create_channel memory management Tim Mooney
- Next:
Re: epicsEvent (posix implementation) bug ? Eric Norum
- 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: epicsEvent (posix implementation) bug ? Till Straumann
- Next:
Re: epicsEvent (posix implementation) bug ? Eric Norum
- 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
|