From owner-freebsd-questions Wed Sep 25 12:39:20 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA15649 for questions-outgoing; Wed, 25 Sep 1996 12:39:20 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA15614 for ; Wed, 25 Sep 1996 12:39:16 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id OAA18984; Wed, 25 Sep 1996 14:38:18 -0500 (EST) From: John Dyson Message-Id: <199609251938.OAA18984@dyson.iquest.net> Subject: Re: Question regarding mmap <--> procfs To: johnson@charming.nrtc.northrop.com Date: Wed, 25 Sep 1996 14:38:18 -0500 (EST) Cc: questions@FreeBSD.org In-Reply-To: <9609251828.AA09743@charming.nrtc.northrop.com> from "johnson@charming.nrtc.northrop.com" at Sep 25, 96 11:28:39 am Reply-To: dyson@FreeBSD.org X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-questions@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > The way I thought I could do this was to use the mmap function in conjunction > with the procfs file /proc/curproc/mem. However, at the moment I can't get > this to work. > > First question: Is what I am trying to do supposed to be possible? (If I > understand mmap and /proc/curproc/mem, it should be possible in principle.) > Ouch!!! mmaping /proc/*/mem doesn't work, and probably won't for a while at least. There are some complex sharing issues that just aren't supported in the current procfs code. John