From owner-freebsd-hackers Tue Feb 27 13:13:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from hand.dotat.at (sfo-gw.covalent.net [207.44.198.62]) by hub.freebsd.org (Postfix) with ESMTP id A048E37B718 for ; Tue, 27 Feb 2001 13:13:35 -0800 (PST) (envelope-from fanf@dotat.at) Received: from fanf by hand.dotat.at with local (Exim 3.20 #3) id 14XrPr-0004DP-00; Tue, 27 Feb 2001 21:12:15 +0000 Date: Tue, 27 Feb 2001 21:12:15 +0000 From: Tony Finch To: Drew Eckhardt Cc: Lyndon Nerenberg , freebsd-hackers@FreeBSD.ORG Subject: Re: [hackers] Re: Setting memory allocators for library functions. Message-ID: <20010227211215.M609@hand.dotat.at> References: <20010227202234.K609@hand.dotat.at> <200102272044.f1RKi0n13690@chopper.Poohsticks.ORG> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200102272044.f1RKi0n13690@chopper.Poohsticks.ORG> Organization: Covalent Technologies, Inc Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Drew Eckhardt wrote: >In message <20010227202234.K609@hand.dotat.at>, dot@dotat.at writes: >>In most cases it is impossible to declare the data read-only because >>it originally had to be read-write and you can't change its attributes >>later. > >mprotect(2). If it's available at all, mprotect() is often limited to memory obtained with mmap(), i.e. not malloc(). Not great for portability. Tony. -- f.a.n.finch fanf@covalent.net dot@dotat.at FORTH: NORTHEAST 6 TO GALE 8 DECREASING 5 OR 6. SLEET. MAINLY MODERATE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message