GNU bug report logs - #35666
[PATCH 0/2] Build a thread-safe hdf5 library

Previous Next

Full log

Message #26 received at 35666 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludovic.courtes <at> inria.fr>
To: Eric Bavier <bavier <at> cray.com>
Cc: Ricardo Wurmus <rekado <at> elephly.net>,
 "35666 <at> debbugs.gnu.org" <35666 <at> debbugs.gnu.org>,
 "pgarlick <at> tourbillion-technology.com" <pgarlick <at> tourbillion-technology.com>
Subject: Re: [bug#35666] [PATCH 0/2] Build a thread-safe hdf5 library
Date: Tue, 14 May 2019 09:28:11 +0200

Hi Eric,

Eric Bavier <bavier <at> cray.com> skribis:

> I think this should be fine, though I've not heard of anyone who has
> relied on this feature.  The "unsupported" part here is that the posix
> lock used for thread-safety is not hoisted into the higher-level API
> calls.  So if your colleague is using the C++ interface and expecting
> thread-safety, they are out of luck.  So the disclaimer is that only
> the low-level C interface gains thread-safety, and the rest are no
> better.

I’m not sure I understand.  Do you mean that, just because you use the
C++ API instead of the C API, the library is not thread-safe?

They do see crashes vanish when using the library compiled with
‘--enable-threadsafe’, and reliably so.

Thanks,
Ludo’.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.