[PATCH] libwbclient clear pointer on bad read

Tue Jan 20 08:42:22 MST 2015

On Tue, Jan 20, 2015 at 02:43:28PM +0000, Matthew Newton wrote:
> There also seems to be an issue as some applications may call
> dlclose() before all threads have exited, causing a segfault at
> thread exit when the TLS destructor is called. Though I think I'd
> personally call it an application bug to call dlclose() when
> threads are still running...

It's the single-threaded application with a thread-aware
libwbclient that I'm worried about. Of course if you are
multi-threaded you should not call dlclose, but it should be
valid to call dlclose in the main thread from my point of
view.

Volker

-- 
SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen
phone: +49-551-370000-0, fax: +49-551-370000-9
AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen
http://www.sernet.de, mailto:kontakt at sernet.de