NTO 1.01 problem ESRCH from sem_wait or sem_trywait

QNX Newsgroups (Archives) qnx.rtos
1

Hi,

I have a problem with application running under old NTO 1.01. It happened 2
times during its lifetime (~ 3 years), that sem_wait or sem_trywait (I do
not know exactly which one of these 2 calls) returned with -1 and errno set
to ESRCH.

My question is: is it possible, that sem_wait or sem_trywait return with -1
ESRCH ? If not, could this be an interference with signal handler calling
mq_send ? Does anybody have this experience ?

Thanks for any advice

Best regards

Lukas Kunc

2

Hi,

I found the answer to my question myself already: sem_trywait sometimes
really returns with -1 and errno set to ESRCH. This happens when NTO is
loaded. I reproduced this in NTO 1.01, but I was not able to reproduce this
in RTOS 6.2.x.

Best regards

Lukas Kunc

“Lukas Kunc” <Lukas.Kunc@gopas.cz> wrote in message
news:chsbnt$3o8$1@inn.qnx.com…

Hi,

I have a problem with application running under old NTO 1.01. It happened
2
times during its lifetime (~ 3 years), that sem_wait or sem_trywait (I do
not know exactly which one of these 2 calls) returned with -1 and errno
set
to ESRCH.

My question is: is it possible, that sem_wait or sem_trywait return
with -1
ESRCH ? If not, could this be an interference with signal handler calling
mq_send ? Does anybody have this experience ?

Thanks for any advice

Best regards

Lukas Kunc