From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10607 invoked by alias); 6 Nov 2011 02:55:33 -0000 Received: (qmail 10595 invoked by uid 22791); 6 Nov 2011 02:55:32 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Received: from mail-fx0-f41.google.com (HELO mail-fx0-f41.google.com) (209.85.161.41) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 06 Nov 2011 02:55:19 +0000 Received: by faaf16 with SMTP id f16so5175239faa.0 for ; Sat, 05 Nov 2011 19:55:17 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.76.66 with SMTP id b2mr36796722fak.15.1320548117702; Sat, 05 Nov 2011 19:55:17 -0700 (PDT) Received: by 10.223.86.200 with HTTP; Sat, 5 Nov 2011 19:55:17 -0700 (PDT) Date: Sun, 06 Nov 2011 02:55:00 -0000 Message-ID: Subject: GDB Python API issues From: Jason Ekstrand To: gdb@sourceware.org Content-Type: text/plain; charset=ISO-8859-1 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/msg00038.txt.bz2 GDB Developers, Hi, I've used GDB for a quite a while now, but have never dug into GDB development. Recently, I started working on a project that heavily abuses GDB's python API. I'm trying to essentially write a more up-to-date replacement for DDD that, instead of parsing GDB output or tying directly into it on a C level, pulls data from inside using GDB's python API. As I've been working on this project, I've started to find all sorts of use cases that the API, as it currently stands, doesn't seem to support. I'm willing to help, but I don't quite know where to start and I wanted to talk to someone before I start submitting a stream of bug reports. Thanks, --Jason Ekstrand