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

To: Joël Krähemann <jkraehemann@gmail.com>
Cc: 923802@bugs.debian.org
Subject: Bug#923802: Acknowledgement (pthread: dead-lock while pthread_cond_destroy())
From: Florian Weimer <fweimer@redhat.com>
Date: Wed, 06 Mar 2019 11:44:47 +0100
Message-id: <[🔎] 87va0wcme8.fsf@oldenburg2.str.redhat.com>
Reply-to: Florian Weimer <fweimer@redhat.com>, 923802@bugs.debian.org
In-reply-to: <[🔎] CA+Owze5LHDCVozV+ih0XznfbAo6-EvaOEVSfx2Os2c8B_44DEg@mail.gmail.com> ("Joël Krähemann"'s message of "Tue, 5 Mar 2019 18:16:34 +0100")
References: <[🔎] 155179933254.6921.14810848040373353472.reportbug@localhost> <handler.923802.B.155179934617637.ack@bugs.debian.org> <[🔎] 155179933254.6921.14810848040373353472.reportbug@localhost> <[🔎] CA+Owze5LHDCVozV+ih0XznfbAo6-EvaOEVSfx2Os2c8B_44DEg@mail.gmail.com> <[🔎] 155179933254.6921.14810848040373353472.reportbug@localhost>

* 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

Reply to:

Follow-Ups:
- Bug#923802: Acknowledgement (pthread: dead-lock while pthread_cond_destroy())
  - From: Joël Krähemann <jkraehemann@gmail.com>

References:
- Bug#923802: pthread: dead-lock while pthread_cond_destroy()
  - From: Joël Krähemann <jkraehemann@gmail.com>
- Bug#923802: Acknowledgement (pthread: dead-lock while pthread_cond_destroy())
  - From: Joël Krähemann <jkraehemann@gmail.com>

Prev by Date: Bug#923802: Acknowledgement (pthread: dead-lock while pthread_cond_destroy())
Next by Date: Bug#923802: Acknowledgement (pthread: dead-lock while pthread_cond_destroy())
Previous by thread: Bug#923802: Acknowledgement (pthread: dead-lock while pthread_cond_destroy())
Next by thread: Bug#923802: Acknowledgement (pthread: dead-lock while pthread_cond_destroy())
Index(es):
- Date
- Thread