Is EINTR possible if there's some third-party code that is catching signals?
Also -- what changes are making? Are you switching vxWorks and RTEMS epicsEvent and epicsMessageQueue to queue-by-priority? Are you taking the wait queue out of the POSIX epicsMessageQueue?
On Jan 31, 2011, at 10:41 AM, Andrew Johnson wrote:
> 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.
>
--
Eric Norum
[email protected]
- Replies:
- Re: epicsEvent (posix implementation) bug ? Andrew Johnson
- References:
- epicsEvent (posix implementation) bug ? Till Straumann
- Re: epicsEvent (posix implementation) bug ? Andrew Johnson
- Re: epicsEvent (posix implementation) bug ? Till Straumann
- Re: epicsEvent (posix implementation) bug ? Andrew Johnson
- Navigate by Date:
- Prev:
Re: epicsEvent (posix implementation) bug ? Andrew Johnson
- Next:
Re: epicsEvent (posix implementation) bug ? Andrew Johnson
- 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 ? Andrew Johnson
- Next:
Re: epicsEvent (posix implementation) bug ? Andrew Johnson
- 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
|