From owner-freebsd-current Sun Mar 2 1:11:20 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C578637B401 for ; Sun, 2 Mar 2003 01:11:19 -0800 (PST) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8874843F75 for ; Sun, 2 Mar 2003 01:11:18 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from gamplex.bde.org (katana.zip.com.au [61.8.7.246]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id UAA16115; Sun, 2 Mar 2003 20:11:12 +1100 Date: Sun, 2 Mar 2003 20:12:54 +1100 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Jun Su Cc: freebsd-current@FreeBSD.ORG Subject: Re: why libkvm not implement read from user memory space In-Reply-To: <200303021352.04325.JunSu@gmx.net> Message-ID: <20030302195626.K29542-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 2 Mar 2003, Jun Su wrote: > I am adding some new feature to the kgdb. I am not sure why the libkvm doesn't > implement reading from memory space when checking core dump. Who can give > some comments on this? If it is possible, I will try to implement it. It was lost when libkvm was converted to use procfs (reading from /proc//mem instead of from kmem). procfs is often considered harmful for even more reasons than this, but replacing it by sysctls tends to break support for dead kernels even more since sysctl() is completely unlike read(). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message