From owner-freebsd-arch@FreeBSD.ORG Tue May 6 08:29:26 2003 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5F44137B401 for ; Tue, 6 May 2003 08:29:26 -0700 (PDT) Received: from gw.nectar.cc (gw.nectar.cc [208.42.49.153]) by mx1.FreeBSD.org (Postfix) with ESMTP id A95A943F93 for ; Tue, 6 May 2003 08:29:25 -0700 (PDT) (envelope-from nectar@celabo.org) Received: from madman.celabo.org (madman.celabo.org [10.0.1.111]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client CN "madman.celabo.org", Issuer "celabo.org CA" (verified OK)) by gw.nectar.cc (Postfix) with ESMTP id 305D5BB; Tue, 6 May 2003 10:29:25 -0500 (CDT) Received: by madman.celabo.org (Postfix, from userid 1001) id 92EB178C66; Tue, 6 May 2003 10:29:26 -0500 (CDT) Date: Tue, 6 May 2003 10:29:26 -0500 From: "Jacques A. Vidrine" To: Harti Brandt Message-ID: <20030506152926.GG77708@madman.celabo.org> Mail-Followup-To: "Jacques A. Vidrine" , Harti Brandt , freebsd-arch@FreeBSD.org References: <20030501182820.GA53641@madman.celabo.org> <20030501191027.GA53801@madman.celabo.org> <20030505110601.H53365@beagle.fokus.fraunhofer.de> <20030505175426.GA19352@madman.celabo.org> <20030506093754.B838@beagle.fokus.fraunhofer.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030506093754.B838@beagle.fokus.fraunhofer.de> X-Url: http://www.celabo.org/ User-Agent: Mutt/1.5.3i-ja.1 cc: freebsd-arch@FreeBSD.org Subject: Re: Re: `Hiding' libc symbols X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 May 2003 15:29:26 -0000 On Tue, May 06, 2003 at 09:46:12AM +0200, Harti Brandt wrote: > No. If I define my own printf() I want that printf to be called even by > library internal calls. No, you really don't. If you do, then you use the techniques that dozens of applications already use today. `Hiding' libc symbols do not get in the way of these techniques. printf is an incredibly bad example, of course. What makes you think there are any calls to printf in libc anyway? Cheers, -- Jacques Vidrine . NTT/Verio SME . FreeBSD UNIX . Heimdal nectar@celabo.org . jvidrine@verio.net . nectar@freebsd.org . nectar@kth.se