From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750994AbWFLKrQ (ORCPT ); Mon, 12 Jun 2006 06:47:16 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751843AbWFLKrQ (ORCPT ); Mon, 12 Jun 2006 06:47:16 -0400 Received: from liaag2ab.mx.compuserve.com ([149.174.40.153]:16618 "EHLO liaag2ab.mx.compuserve.com") by vger.kernel.org with ESMTP id S1750994AbWFLKrP (ORCPT ); Mon, 12 Jun 2006 06:47:15 -0400 Date: Mon, 12 Jun 2006 06:42:42 -0400 From: Chuck Ebbert <76306.1226@compuserve.com> Subject: Next-gen ptrace? To: Ingo Molnar Cc: linux-kernel Message-ID: <200606120644_MC3-1-C231-6147@compuserve.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Sun, 11 Jun 2006 09:32:14 +0200, Ingo Molnar wrote: > Some of the GUIs try to do something about this and automate crash > reporting, but it doesnt cover most of the app crashes and userspace > clearly needs kernel help, because ptrace is too inflexible for this > purpose. (help is on the way though, there's a next-gen ptrace > project that solves these problems very cleanly.) Where is this next-gen ptrace project? I can't find it. -- Chuck