From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22539 invoked by alias); 17 Sep 2002 16:33:25 -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 22532 invoked from network); 17 Sep 2002 16:33:25 -0000 Received: from unknown (HELO localhost.redhat.com) (216.138.202.10) by sources.redhat.com with SMTP; 17 Sep 2002 16:33:25 -0000 Received: from ges.redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 9D2873DAA for ; Tue, 17 Sep 2002 12:33:25 -0400 (EDT) Message-ID: <3D875955.9040508@ges.redhat.com> Date: Tue, 17 Sep 2002 09:33:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.0) Gecko/20020824 X-Accept-Language: en-us, en MIME-Version: 1.0 To: gdb@sources.redhat.com Subject: Viewing the symbol table as a database? Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-09/txt/msg00224.txt.bz2 Hello, Should core GDB view the symbol table as a database. That way the internals are really abstracted. For instance, instead of pc->block->nametab->symbol, just do: lookup_symbol (symtab, pc, "name"); Disclaimer: this isn't my idea but I think it is good. It will let the data structures scale beyond currend address space limitations. Andrew