[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: bugs in gnulib thread modules
From: |
Bruno Haible |
Subject: |
Re: bugs in gnulib thread modules |
Date: |
Thu, 05 Jan 2017 20:15:42 +0100 |
User-agent: |
KMail/4.8.5 (Linux/3.8.0-44-generic; KDE/4.8.5; x86_64; ; ) |
Torvald Riegel wrote:
> I found two bugs just by briefly scanning through the current
> lib/glthread/lock.c. As a hint, I'll just mention double-checked
> locking and order of destruction. And skipping destruction is of course
> not correct in the general case either (unless I'm misreading
> lib/glthread/cond.c, for example).
Can you give line numbers, please? lib/glthread/lock.c and lib/glthread/cond.c
are large files. If you have found bugs there, *of course* I want to have
them fixed.
Bruno
- Re: Test-lock hang (not 100% reproducible) on GNU/Linux, (continued)
- Re: Test-lock hang (not 100% reproducible) on GNU/Linux, Pavel Raiskup, 2017/01/04
- Re: Test-lock hang (not 100% reproducible) on GNU/Linux, Bruno Haible, 2017/01/04
- Re: Test-lock hang (not 100% reproducible) on GNU/Linux, Pavel Raiskup, 2017/01/04
- Re: Test-lock hang (not 100% reproducible) on GNU/Linux, Pavel Raiskup, 2017/01/04
- Re: Test-lock hang (not 100% reproducible) on GNU/Linux, Bruno Haible, 2017/01/04
Re: Test-lock hang (not 100% reproducible) on GNU/Linux, Bruno Haible, 2017/01/05
Re: Test-lock hang (not 100% reproducible) on GNU/Linux, Torvald Riegel, 2017/01/05
- Re: bugs in gnulib thread modules,
Bruno Haible <=
Re: C11 atomics, Bruno Haible, 2017/01/05
Re: read-write locks, Bruno Haible, 2017/01/05