On vxworks, after destroying the semaphore used to implement a mutex,
__gthread_mutex_lock fails and __gnu_cxx::__mutex::lock calls
__throw_concurrence_lock_error. Nothing ensures the mutex_pool
mutexes survive init-once objects containing _Safe_sequence_base. If
such an object completes constr
On Feb 17, 2023, Alexandre Oliva wrote:
> On vxworks, after destroying the semaphore used to implement a mutex,
> __gthread_mutex_lock fails and __gnu_cxx::__mutex::lock calls
> __throw_concurrence_lock_error. Nothing ensures the mutex_pool
> mutexes survive init-once objects containing _Safe_se
On Fri, 17 Feb 2023, 08:02 Alexandre Oliva via Libstdc++, <
libstd...@gcc.gnu.org> wrote:
> On Feb 17, 2023, Alexandre Oliva wrote:
>
> > On vxworks, after destroying the semaphore used to implement a mutex,
> > __gthread_mutex_lock fails and __gnu_cxx::__mutex::lock calls
> > __throw_concurrence
On 17/02/23 09:01, Alexandre Oliva via Libstdc++ wrote:
On Feb 17, 2023, Alexandre Oliva wrote:
On vxworks, after destroying the semaphore used to implement a mutex,
__gthread_mutex_lock fails and __gnu_cxx::__mutex::lock calls
__throw_concurrence_lock_error. Nothing ensures the mutex_pool
mu
