Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 20 Jun 2002 17:46:08 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 20 Jun 2002 17:46:07 -0400 Received: from beach.cise.ufl.edu ([128.227.205.211]:50654 "EHLO mail.cise.ufl.edu") by vger.kernel.org with ESMTP id ; Thu, 20 Jun 2002 17:46:06 -0400 Date: Thu, 20 Jun 2002 17:46:07 -0400 (EDT) From: Pradeep Padala To: Andrew D Kirch Cc: "linux-kernel@vger.kernel.org" Subject: Re: ptrace vs /proc In-Reply-To: <20020620163648.6d5e7955.Trelane@Trelane.Net> Message-ID: 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: 1034 Lines: 21 > Linux already posesses modular support for a /proc filesystem, every distribution, and I believe the stock kernel config includes support for this under the filesystems section by default. I should have been clearer. I would like to know about the features ptrace supports like "system call tracing", "setting breakpoints" etc. Traditionally they were done through ptrace interface. In solaris and I guess in other operating systems like IRIX, they are moved to /proc interface. Applications wanting to trace programs like gdb, would use ioctl on the /proc/ and trace the programs. As far as I could investigate, I didn't find any such interface in linux. Programs like strace do the tracing through ptrace only. Please let me know if you know more about this. --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/