Re: potential deadlock in _once

2018-03-06 Thread Sebastian Huber
On 06/03/18 12:12, Passas, Stavros wrote: -Original Message- From: Sebastian Huber [mailto:sebastian.hu...@embedded-brains.de] Sent: Tuesday, March 6, 2018 10:19 AM To: Passas, Stavros;rtems-de...@rtems.org Subject: Re: potential deadlock in _once Yes, please open a ticket and

RE: potential deadlock in _once

2018-03-06 Thread Passas, Stavros
-Original Message- From: Sebastian Huber [mailto:sebastian.hu...@embedded-brains.de] Sent: Tuesday, March 6, 2018 10:19 AM To: Passas, Stavros ; rtems-de...@rtems.org Subject: Re: potential deadlock in _once > Yes, please open a ticket and provide a test case for the RTEMS test su

Re: potential deadlock in _once

2018-03-06 Thread Sebastian Huber
On 04/03/18 22:09, Passas, Stavros wrote: Hi, We have faced RTEMS threads getting locked up when using certain c++ functionality. Issue happens for example when std::future is combined with std::async. Investigating deeper, seems like this happens if std::async executes before std::future