From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1707 invoked by alias); 17 Sep 2002 19:41:32 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 1700 invoked from network); 17 Sep 2002 19:41:32 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by sources.redhat.com with SMTP; 17 Sep 2002 19:41:32 -0000 Received: from nevyn.them.org ([66.93.61.169] ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 17rP9y-0004MD-00; Tue, 17 Sep 2002 15:41:27 -0500 Received: from drow by nevyn.them.org with local (Exim 3.35 #1 (Debian)) id 17rODv-0007Q9-00; Tue, 17 Sep 2002 15:41:27 -0400 Date: Tue, 17 Sep 2002 12:41:00 -0000 From: Daniel Jacobowitz To: Andrew Cagney Cc: David Carlton , gdb Subject: Re: struct environment Message-ID: <20020917194127.GA28509@nevyn.them.org> Mail-Followup-To: Andrew Cagney , David Carlton , gdb References: <3D86DE18.6030003@ges.redhat.com> <20020917134057.GA26237@nevyn.them.org> <3D875149.9080502@ges.redhat.com> <20020917160700.GA20451@nevyn.them.org> <3D876C3F.2090401@ges.redhat.com> <20020917180211.GA23552@nevyn.them.org> <3D878496.6010201@ges.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3D878496.6010201@ges.redhat.com> User-Agent: Mutt/1.5.1i X-SW-Source: 2002-09/txt/msg00234.txt.bz2 On Tue, Sep 17, 2002 at 03:37:58PM -0400, Andrew Cagney wrote: > > >>Depends on how you grow it :-) Something like (assuming a real language > >>:-): > >> D: > >> 0: x, z > >> 1: x, y (from C) > >> 2: ... > > > > > >How you intend to do this efficiently I don't know. > > By efficiency did you mean speed or memory? I don't see speed being an > issue (except for the global table), just memory (GDB's foot print growing). Either. It's quite a hard problem, which is a reason why C++ compilers generally use Koenig lookup through multiple blocks rather than growing blocks. And there's all sorts of other correctness issues. > > Remember that C > > uses D in turn, and that things "using"'d into D will therefore be > > visible in C. > > True, but I'm not the one implementing this. I'm just trying to > understand the core-gdb interface. > > Andrew > > > -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer