Bug#923802: marked as done (pthread: dead-lock while pthread_cond_destroy())

2019-03-06 Thread Debian Bug Tracking System
Your message dated Wed, 06 Mar 2019 13:13:36 +0100 with message-id <877edccia7@oldenburg2.str.redhat.com> and subject line Re: Bug#923802: Acknowledgement (pthread: dead-lock while pthread_cond_destroy()) has caused the Debian Bug report #923802, regarding pthread: dead-lock while

Bug#923802: Acknowledgement (pthread: dead-lock while pthread_cond_destroy())

2019-03-06 Thread Joël Krähemann
Hi, Yes, it is an application bug. So, I fixed my upstream source. Just recognized calling pthread_cond_destroy() twice, later. Best regards, Joël On Wed, Mar 6, 2019 at 11:44 AM Florian Weimer wrote: > > * Joël Krähemann: > > > This happens as you call pthread_cond_destroy() twice on the very

Bug#923802: Acknowledgement (pthread: dead-lock while pthread_cond_destroy())

2019-03-06 Thread Florian Weimer
* Joël Krähemann: > This happens as you call pthread_cond_destroy() twice on the very same > cond variable. Surely that's an application bug. Why do you think this is a glibc issue? Thanks, Florian