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() tw

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

2019-03-05 Thread Joël Krähemann
Hi, This happens as you call pthread_cond_destroy() twice on the very same cond variable. Just attached a file to reproduce. Bests, Joël On Tue, Mar 5, 2019 at 4:27 PM Debian Bug Tracking System wrote: > > Thank you for filing a new Bug report with Debian. > > You can follow progress on this

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

2019-03-05 Thread Joël Krähemann
Package: libc0.1-dev Version: 2.25-2 Severity: normal File: pthread Dear Maintainer, As checking why GSequencer's test didn't continue, I have discovered a dead-lock as calling pthread_cond_destroy() http://salsa.debian.org/multimedia-team/gsequencer Here is the command to reproduce: