On 6/11/2019 4:52 AM, Corinna Vinschen wrote:
> On Jun 7 12:10, Ken Brown wrote:
>> While testing some new pipe code, I'm occasionally seeing a timerfd deadlock:
>> The main thread is stuck in timerfd_tracker::dtor at timerfd.cc:354, waiting
>> for
>> the timerfd
On 6/11/2019 4:52 AM, Corinna Vinschen wrote:
> On Jun 7 12:10, Ken Brown wrote:
>> While testing some new pipe code, I'm occasionally seeing a timerfd deadlock:
>> The main thread is stuck in timerfd_tracker::dtor at timerfd.cc:354, waiting
>> for
>> the timerfd
On Jun 7 12:10, Ken Brown wrote:
> While testing some new pipe code, I'm occasionally seeing a timerfd deadlock:
> The main thread is stuck in timerfd_tracker::dtor at timerfd.cc:354, waiting
> for
> the timerfd thread to close; and the timerfd thread is stuck at
> timerf
While testing some new pipe code, I'm occasionally seeing a timerfd deadlock:
The main thread is stuck in timerfd_tracker::dtor at timerfd.cc:354, waiting
for
the timerfd thread to close; and the timerfd thread is stuck at timerfd.cc:140,
waiting to acquire a mutex that'
4 matches
Mail list logo
