Date: Thu, 1 May 2003 11:01:19 -0500 From: "Jacques A. Vidrine" <nectar@FreeBSD.org> To: "Andrey A. Chernov" <ache@nagual.pp.ru> Cc: freebsd-arch@FreeBSD.org Subject: Re: `Hiding' libc symbols Message-ID: <20030501160119.GB35367@madman.celabo.org> In-Reply-To: <20030501155342.GA55078@nagual.pp.ru> References: <20030430152708.GA26216@madman.celabo.org> <20030430153645.GL39658@survey.codeburst.net> <20030430164135.GB26508@madman.celabo.org> <20030501140255.GB1869@survey.codeburst.net> <20030501143032.GA34163@madman.celabo.org> <20030501144600.GC1869@survey.codeburst.net> <20030501145345.GA34884@madman.celabo.org> <20030501151458.GA54182@nagual.pp.ru> <20030501152251.GB34992@madman.celabo.org> <20030501155342.GA55078@nagual.pp.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, May 01, 2003 at 07:53:42PM +0400, Andrey A. Chernov wrote:
> On Thu, May 01, 2003 at 10:22:51 -0500, Jacques A. Vidrine wrote:
> >
> > I'm with you ... as long as:
>
> So, we can right now back out strlcpy hack at least to minimize future
> work.
No, that does not follow. strlcpy does not add work for any future
solution, and besides, it is not the future yet.
> It have nothing common with threads, namespace.h is for.
No, you are mistaken.
namespace.h
39 /*
40 * ISO C (C90) section. Most names in libc aren't in ISO C, so they
41 * should be here. Most aren't here...
42 */
43 #define err _err
44 #define warn _warn
45 #define nsdispatch _nsdispatch
46 #define strlcat _strlcat
47 #define strlcpy _strlcpy
The comment dates back to 2001.
> Saving libc
> but not saving other libs application can be linked to gains really
> nothing.
That is your opinion, and one I do not share. I did not make the
commit for no purpose.
[...]
> > (b) We give Daniel and others working on threaded libraries a chance
> > to discuss the special needs there. (That _is_ why namespace.h
> > was originally created. We do need to handle stubs somehow; weak
> > symbols alone are not enough.)
>
> See my another reply (to Daniel) about threads.
I saw it and I think you are mistaken.
> > (d) I don't have to do it all.
>
> I too. :-) Most of work will be to change current threads tricks to
> prevent them be explotable from outside of libc/libc_r/etc, i.e. to be
> true internal. It is for our threads team who introduce namespace.h
No, I do not think this is a threads-only issue.
Cheers,
--
Jacques Vidrine . NTT/Verio SME . FreeBSD UNIX . Heimdal
nectar@celabo.org . jvidrine@verio.net . nectar@freebsd.org . nectar@kth.se
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030501160119.GB35367>