[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 22:09:38 +0100 |
User-agent: |
KMail/4.8.5 (Linux/3.8.0-44-generic; KDE/4.8.5; x86_64; ; ) |
Torvald Riegel wrote:
> > 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.
>
> I can understand both points. However, I'd suggest that you first try
> to find them (or that whoever maintains these files does); this is often
> a good exercise, and helps make oneself sensitive for concurrency
> problems. If you don't want to do that first, I can give details.
We don't need to play "teacher and student" games here. I hold a 'Dr.',
like you. I have experience in other areas than you. If I wasn't
sensitive for concurrency problems, I wouldn't have introduced the
'lock' module in gnulib.
Can you please do me the favour and tell the line numbers of the two
observations that you spotted? Thanks.
Bruno
- Re: Test-lock hang (not 100% reproducible) on GNU/Linux, (continued)
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: C11 atomics, Bruno Haible, 2017/01/05
Re: read-write locks, Bruno Haible, 2017/01/05
Re: read-write locks, Bruno Haible, 2017/01/05