From owner-freebsd-arch Sat Feb 9 8:40:25 2002 Delivered-To: freebsd-arch@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 4DF2A37B417 for ; Sat, 9 Feb 2002 08:40:18 -0800 (PST) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id g19Gd2D32061; Sat, 9 Feb 2002 11:39:02 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Sat, 9 Feb 2002 11:39:02 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Julian Elischer Cc: Peter Wemm , Daniel Eischen , Dan Eischen , arch@FreeBSD.ORG Subject: Re: getsetcontext system call In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 9 Feb 2002, Julian Elischer wrote: > ptrace doesn't use procfs as it is... It used to be the case that the majority of our debugging tools relied heavily on /proc to function, and that the ptrace() implementation had hooks into the procfs implementation (although it didn't actually require that /proc be mounted). Happily, DES has invested time in both reducing dependencies (truss, for example), and cleaning up procfs, so things are much improved. There are still a few dependencies, but the only one that really comes to mind is that 'procfs -e' relies on /proc/pid/mem to find environmental variables. Mind you, I'm not objecting to procfs learning about KSE, threads, etc, I just want to avoid requiring it in order to have a useful debugging environment. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message