Date: Fri, 04 Mar 2005 11:24:49 +0800 From: David Xu <davidxu@freebsd.org> To: Julian Elischer <julian@elischer.org> Cc: threads@freebsd.org Subject: Re: patch for threads/76690 - critical - fork hang in child for -lc_r Message-ID: <4227D501.8090706@freebsd.org> In-Reply-To: <422773C2.8090607@elischer.org> References: <Pine.GSO.4.43.0503021042310.26125-100000@sea.ntplx.net> <000b01c51fbb$4189ea30$090210ac@BORJA> <422773C2.8090607@elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
4.x does not have a __malloc_lock symbol exported, I had suggested to add __malloc_lock in FreeBSD 5 libpthread since I saw some broken applications call malloc in child process after fork() and before execv(). :) Julian Elischer wrote: > the bug is still valid in 4.x > > > Andriy Tkachuk wrote: > >>> Is there a reason you are still using libc_r? >>> >> >> >> I don't use it at all, but there was critical bug >> i threads-pr - so i just decided to fix it since i >> have had some time ) >> >> If this library is needless, why is it still there >> and this pr in criticals? >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4227D501.8090706>