Date: Mon, 18 Apr 2005 13:15:46 -0500 From: Archie Cobbs <archie@dellroad.org> To: Daniel Eischen <deischen@freebsd.org> Cc: freebsd-threads@freebsd.org Subject: Re: Bug with pthread_getspecific() and signals Message-ID: <4263F952.1000106@dellroad.org> In-Reply-To: <Pine.GSO.4.43.0504181354560.58-100000@sea.ntplx.net> References: <Pine.GSO.4.43.0504181354560.58-100000@sea.ntplx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Daniel Eischen wrote: >>If it does, can you show me in which FreeBSD releases the bug is fixed? > > I don't know if it ever got fixed in libc_r. > > ... > > It should work correctly in both libpthread and libthr. > libc_r is not being maintained. Thanks.. unfortunately I'm not familiar with the exact history of FreeBSD's thread libraries. Can you help me understand how to detect/workaround this problem in my configure script? E.g., I need to know: - In what versions of FreeBSD will "-pthread" result in a non-broken (with respect to this bug) thread library? - Of the earlier versions of FreeBSD, in which ones is there a viable workaround and what is it (e.g., "-lpthread" instead of "-pthread"?) This bug makes my application basically useless so it's critical to understand when and how I can work around it. I'd like to add logic to the configure script to determine either (a) to give up, or (b) what the appropriate linker flag is, given the version of FreeBSD. Thanks, -Archie __________________________________________________________________________ Archie Cobbs * CTO, Awarix * http://www.awarix.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4263F952.1000106>