From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2970 invoked by alias); 5 Feb 2008 13:18:26 -0000 Received: (qmail 2962 invoked by uid 22791); 5 Feb 2008 13:18:25 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 05 Feb 2008 13:18:02 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id E393698100; Tue, 5 Feb 2008 13:18:00 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id CFEC1980E0; Tue, 5 Feb 2008 13:18:00 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.68) (envelope-from ) id 1JMNgW-0002qi-1I; Tue, 05 Feb 2008 08:18:00 -0500 Date: Tue, 05 Feb 2008 13:18:00 -0000 From: Daniel Jacobowitz To: Mark Kettenis Cc: ghost@cs.msu.su, gdb@sources.redhat.com Subject: Re: Variable objects and STL containers Message-ID: <20080205131800.GB10652@caradoc.them.org> Mail-Followup-To: Mark Kettenis , ghost@cs.msu.su, gdb@sources.redhat.com References: <18343.64413.689019.489727@kahikatea.snap.net.nz> <200802051131.m15BV7kd006854@brahms.sibelius.xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200802051131.m15BV7kd006854@brahms.sibelius.xs4all.nl> User-Agent: Mutt/1.5.17 (2007-12-11) X-IsSubscribed: yes 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: 2008-02/txt/msg00024.txt.bz2 On Tue, Feb 05, 2008 at 12:31:07PM +0100, Mark Kettenis wrote: > > We discussed using Python scripting for that; in fact, I have a patch locally > > that will make > > > > -var-evaluate-expression V > > > > for a vector print something like: > > > > [1,2,3] > > > > I'm working on making those element the children of the variable object, > > but it's not done yet. > > Still this means that you'll need to write python code for each and > every STL implementation, and play catchup whenever the implementation > is changed. I guess the only way to get this to work is to connvince > the GCC people to maintain the python code together with libstdc++. Right. That's what I would like to happen; and since GCC is both a GNU project and widely used with GDB, I think it will be easy to convince them. I envision these scripts going in /usr/share/gdb/packages or something similar to that. -- Daniel Jacobowitz CodeSourcery