From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16880 invoked by alias); 7 Nov 2011 13:28:59 -0000 Received: (qmail 16871 invoked by uid 22791); 7 Nov 2011 13:28:59 -0000 X-SWARE-Spam-Status: No, hits=-7.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD,SPF_HELO_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 07 Nov 2011 13:28:20 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id pA7DSJjQ024460 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 7 Nov 2011 08:28:19 -0500 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id pA7DSIig019093; Mon, 7 Nov 2011 08:28:18 -0500 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id pA7DSGAW021590; Mon, 7 Nov 2011 08:28:17 -0500 From: Tom Tromey To: Jason Ekstrand Cc: gdb@sourceware.org Subject: Re: GDB Python API issues References: Date: Mon, 07 Nov 2011 13:28:00 -0000 In-Reply-To: (Jason Ekstrand's message of "Sat, 5 Nov 2011 21:55:17 -0500") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.90 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2011-11/txt/msg00046.txt.bz2 >>>>> "Jason" == Jason Ekstrand writes: Jason> Hi, I've used GDB for a quite a while now, but have never dug into GDB Jason> development. Recently, I started working on a project that heavily Jason> abuses GDB's python API. I'm trying to essentially write a more Jason> up-to-date replacement for DDD that, instead of parsing GDB output or Jason> tying directly into it on a C level, pulls data from inside using Jason> GDB's python API. You could also simply put the GUI inside of gdb... :) The 'gdb.post_event' function basically exists so you can do this and run the GUI in a separate thread. Jason> As I've been working on this project, I've started to find all sorts Jason> of use cases that the API, as it currently stands, doesn't seem to Jason> support. I'm willing to help, but I don't quite know where to start Jason> and I wanted to talk to someone before I start submitting a stream of Jason> bug reports. You can bring up ideas and problems here on the list if you like. A stream of bug reports would also be ok. Tom