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
* 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
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
3 matches
Mail list logo