Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 2 Jul 2002 21:15:48 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 2 Jul 2002 21:15:47 -0400 Received: from beach.cise.ufl.edu ([128.227.205.211]:3288 "EHLO mail.cise.ufl.edu") by vger.kernel.org with ESMTP id ; Tue, 2 Jul 2002 21:15:47 -0400 Date: Tue, 2 Jul 2002 21:18:11 -0400 (EDT) From: Pradeep Padala To: David Wagner Cc: "linux-kernel@vger.kernel.org" Subject: Re: ptrace vs /proc In-Reply-To: Message-ID: References: <1024609747.922.0.camel@sinai> <20020702004706.GB107@elf.ucw.cz> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 834 Lines: 18 > The Solaris /proc implementation, in contrast, was much cleaner, > in my experience. I suspect this is partially because the Solaris > implementation was more carefully thought-through, but also the interface > helped: by not overloading the meaning of signals, the Solaris /proc > interface avoids changing the semantics of signal-related functionality > in the traced process, and this makes for cleaner code. I completely agree with you. Using ptrace to do user level extensions like UFO(http://www.cs.ucsb.edu/projects/ufo/index.html) is grossly inefficient and kludgy. --pradeep - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/