Bug#906917: sem_timedwait could always block and returns ETIMEOUT but decrements the value on i686 architecture

2019-01-16 Thread Андрей Доценко
I've made all sem_timedwait work. One of the libraries was missing *pthread* linkage but was linked to a process that links to pthread itself. Message > undefined reference to symbol 'sem_timedwait@@GLIBC_2.2' > was not shown in the project. But it is shown it the test case if I remove pthread

Bug#906917: sem_timedwait could always block and returns ETIMEOUT but decrements the value on i686 architecture

2019-01-14 Thread Андрей Доценко
appen" in a project that follows CERT recommendations. I'll try to debug it separately. The problem is floating as I see. пн, 14 янв. 2019 г. в 12:48, Андрей Доценко : > No, we use single architecture for all the processes. Our software works > fine with Ubuntu 14.04 (i386 and amd64 versio

Bug#906917: sem_timedwait could always block and returns ETIMEOUT but decrements the value on i686 architecture

2019-01-11 Thread Андрей Доценко
in our embedded systems. Codebase is about 1000 source files. But the minimal test passes without ASAN so I cannot determine what affects sem_timedwait in our project. Any thoughts? вс, 30 дек. 2018 г. в 22:31, Aurelien Jarno : > Hi, > > On 2018-08-22 13:02, Андрей Доценко wrote: > > Packa

Bug#906917: sem_timedwait could always block and returns ETIMEOUT but decrements the value on i686 architecture

2019-01-14 Thread Андрей Доценко
No, we use single architecture for all the processes. Our software works fine with Ubuntu 14.04 (i386 and amd64 versions) and Debian 9 (amd64). Only Denian 9 i386 has this problem. Problem reproduced with Docker i386 container too. At the first time problem has been found in the Docker image, so I