From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5427 invoked by alias); 14 Jul 2008 20:54:09 -0000 Received: (qmail 5418 invoked by uid 22791); 14 Jul 2008 20:54:08 -0000 X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 14 Jul 2008 20:53:50 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id m6EKrm6H003922 for ; Mon, 14 Jul 2008 16:53:48 -0400 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [10.11.255.20]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m6EKrlvn020163; Mon, 14 Jul 2008 16:53:48 -0400 Received: from opsy.redhat.com (vpn-12-60.rdu.redhat.com [10.11.12.60]) by pobox.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m6EKrlvc030582; Mon, 14 Jul 2008 16:53:47 -0400 Received: by opsy.redhat.com (Postfix, from userid 500) id A9333508080; Mon, 14 Jul 2008 14:53:46 -0600 (MDT) To: Keith Seitz Cc: Insight List Subject: Re: insight build, plus patch request References: <487BAD18.8040607@redhat.com> <487BBA39.1050207@redhat.com> From: Tom Tromey Reply-To: Tom Tromey X-Attribution: Tom Date: Mon, 14 Jul 2008 20:54:00 -0000 In-Reply-To: <487BBA39.1050207@redhat.com> (Keith Seitz's message of "Mon\, 14 Jul 2008 13\:42\:33 -0700") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact insight-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-owner@sourceware.org X-SW-Source: 2008-q3/txt/msg00005.txt.bz2 Keith> Good case for PyGtk, for sure, but unless I went with 100% GDB/MI Keith> implementation (which I don't want to do), I would still need to Keith> either rewrite or recycle all the glue code in gdbtk/generic. I think we'll need that stuff anyhow, just for plain Python scripting in gdb. Some of the hooks are in weird spots, but a lot of them just seem like natural places to want to get information or insert some processing. Keith> Once again, it may simply not be worth the effort any more. It might Keith> be better to simply contribute to =C3=98yvind Harboe's stand-alone C= DT Keith> debugger. Or nemiver or kdevelop or ... :-) Tom