From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20428 invoked by alias); 12 Sep 2005 22:37:05 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 20407 invoked by uid 22791); 12 Sep 2005 22:37:00 -0000 Received: from are.twiddle.net (HELO are.twiddle.net) (64.81.246.98) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Mon, 12 Sep 2005 22:37:00 +0000 Received: from are.twiddle.net (localhost.localdomain [127.0.0.1]) by are.twiddle.net (8.12.11/8.12.11) with ESMTP id j8CMacI1003622; Mon, 12 Sep 2005 15:36:38 -0700 Received: (from rth@localhost) by are.twiddle.net (8.12.11/8.12.11/Submit) id j8CMabO4003621; Mon, 12 Sep 2005 15:36:37 -0700 Date: Mon, 12 Sep 2005 22:37:00 -0000 From: Richard Henderson To: Mark Kettenis Cc: drow@false.org, amodra@bigpond.net.au, gdb-patches@gcc.gnu.org, Richard Henderson Subject: Re: ppc32 debugging ppc64, part 1 Message-ID: <20050912223637.GA3587@twiddle.net> References: <20050912125047.GA5411@twiddle.net> <200509121947.j8CJlT1H030779@elgar.sibelius.xs4all.nl> <20050912203220.GA10796@nevyn.them.org> <200509122119.j8CLJDNE020689@elgar.sibelius.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200509122119.j8CLJDNE020689@elgar.sibelius.xs4all.nl> User-Agent: Mutt/1.4.1i X-SW-Source: 2005-09/txt/msg00095.txt.bz2 On Mon, Sep 12, 2005 at 11:19:13PM +0200, Mark Kettenis wrote: > ...but in that case Richard is making things hopelessly complicated by > doing using syscall() instead of ptrace(). I'm undecided as to whether it's cleaner or more complicated. On the one hand, I don't have to add odd casts and can just use a pointer as the real interface allows. But for the record, I was seeing odd things and wanted to get the libc code out of the way. I later discovered the typo in my own code, but I never got around to reverting the use of syscall. > Fair enough. But this code is really getting difficult to read. It > uses several constructs that really only made sense in the generic > code where this was copied from. Huh? I removed the bulk of those. What in particular did you have in mind? > What really frustrates me is that the different Linux ports are > reinventing the wheel, all in a different way. I appreciate your frustration, but it's not something that's in my purvey to think about. Ptrace is so hopelessly obtuse, slow, and indirect that any effort fixing it would be better spent designing a proper interface. And in the meantime there's the issue of what's actually present in extant kernels. r~