Date: Tue, 22 Jun 2004 16:08:21 -0500 From: Dan Nelson <dnelson@allantgroup.com> To: Daniel Eischen <eischen@vigrid.com> Cc: Chris Stenton <jacs@gnome.co.uk> Subject: Re: pthread - fork - execv problem Message-ID: <20040622210820.GA17392@dan.emsphone.com> In-Reply-To: <Pine.GSO.4.10.10406221614470.17576-100000@pcnet5.pcnet.com> References: <20040622182632.GJ86471@dan.emsphone.com> <Pine.GSO.4.10.10406221614470.17576-100000@pcnet5.pcnet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Jun 22), Daniel Eischen said: > > libpthread in -current does support pthread_atfork, and I have a > > patch (below) that adds the same functionality to libc_r and libthr > > that I need to send-pr. Pointy hat to the original committer for > > breaking ABI compatibility. http://dan.allantgroup.com/FreeBSD/ > > Whaa? Adding a function doesn't break ABI, and I don't want to > maintain 3 thread libraries. It does if an application detects pthread_fork during configure and uses it. You then can't use libmap to redirect libpthread to one of the other thread libraries for testing, since you'll get an undefined symbol error at runtime. Nikos Ntarmos also noticed that there's no pthread_atfork manpage. We could probably just use the Single Unix one. -- Dan Nelson dnelson@allantgroup.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040622210820.GA17392>