From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16220 invoked by alias); 30 Jan 2008 13:18:05 -0000 Received: (qmail 16209 invoked by uid 22791); 30 Jan 2008 13:18:04 -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; Wed, 30 Jan 2008 13:17:44 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 4FA1498151; Wed, 30 Jan 2008 13:17:43 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id E5F6998005; Wed, 30 Jan 2008 13:17:42 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.68) (envelope-from ) id 1JKCow-0003fN-39; Wed, 30 Jan 2008 08:17:42 -0500 Date: Wed, 30 Jan 2008 13:52:00 -0000 From: Daniel Jacobowitz To: Pierre Muller Cc: 'Vladimir Prus' , gdb-patches@sources.redhat.com Subject: Re: [RFA] Use vector for varobj_list_children interface. Message-ID: <20080130131742.GC13702@caradoc.them.org> Mail-Followup-To: Pierre Muller , 'Vladimir Prus' , gdb-patches@sources.redhat.com References: <200801171755.47572.vladimir@codesourcery.com> <20080129215240.GG15063@caradoc.them.org> <200801301019.53604.vladimir@codesourcery.com> <000001c86319$2cfcb3f0$86f61bd0$@u-strasbg.fr> <000101c8631b$aa13cbb0$fe3b6310$@u-strasbg.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000101c8631b$aa13cbb0$fe3b6310$@u-strasbg.fr> User-Agent: Mutt/1.5.17 (2007-12-11) X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2008-01/txt/msg00788.txt.bz2 On Wed, Jan 30, 2008 at 09:39:44AM +0100, Pierre Muller wrote: > I think it is the part used by insight Correct. Our position is that Insight is not part of GDB and the GDB developers are not responsible for fixing it; it's unfortunate if it breaks, but the Insight maintainers are generally good about fixing it up later (Keith in particular). > If you send it back to the list, I can test it and check it in > as obvious fix on your behalf. > > Daniel, is that OK? I'm not going to stop anyone from fixing Insight, but I don't feel obliged to do it myself. -- Daniel Jacobowitz CodeSourcery