From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28092 invoked by alias); 19 May 2003 14:03:17 -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 28080 invoked from network); 19 May 2003 14:03:16 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 19 May 2003 14:03:16 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id h4JE3GH11719 for ; Mon, 19 May 2003 10:03:16 -0400 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [172.16.52.156]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h4JE3GI25662 for ; Mon, 19 May 2003 10:03:16 -0400 Received: from localhost.redhat.com (IDENT:rOK6okjz79kRrTszG90IL/Y6UlKiRlMH@tooth.toronto.redhat.com [172.16.14.29]) by pobox.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h4JE3Fo01582 for ; Mon, 19 May 2003 10:03:15 -0400 Received: by localhost.redhat.com (Postfix, from userid 469) id 94A772C43B; Mon, 19 May 2003 10:08:35 -0400 (EDT) From: Elena Zannoni MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16072.58723.23345.182059@localhost.redhat.com> Date: Mon, 19 May 2003 14:03:00 -0000 To: Mark Kettenis Cc: gdb@sources.redhat.com Subject: Re: [PATCH] Naming dwarves In-Reply-To: <200305171253.h4HCrTT0012142@elgar.kettenis.dyndns.org> References: <200305171253.h4HCrTT0012142@elgar.kettenis.dyndns.org> X-SW-Source: 2003-05/txt/msg00267.txt.bz2 Mark Kettenis writes: > Andrew already made a side-remark in an earlier message: how are we > going to name our files and functions related to DWARF? > > There are basically two generations of the DWARF Debugging Information > Format. The first generation is usually referred to as DWARF Version > 1. There is a 1.1.0 revision of the DWARF standard, but this revision > is supposed to be fully binary compatible with the origional DWARF > definition. The second generation is referred to as DWARF Version 2, > or simply DWARF-2. Although the basic structure of Version 2 format > is the very similar to Version 1, the encoding is different. > Therefore these two formats are not binary compatible, which is why we > have seperate DWARF and DWARF-2 symbol readers in GDB. There are also > many new features in DWARF-2. > > There is also a public draft for DWARF Version 3, which should be > largely binary compatible with Version 2. Standardization of Version > 3 seems to have stopped, but some of the proposed extensions are > already in use. I believe our DWARF-2 reader supports these. Since > the Version 3 format is largely binary compatible with Version 2, I > don't think we'll ever have a seperate DWARF-3 reader in GDB. The > number of new features in the proposed standard is rather limited. > > Currently we have the following files dealing with DWARF: > > DWARF Version 1: > dwarfread.c > > DWARF Version 2: > dwarf2read.c > dwarf2expr.c dwarf2expr.h > dwarf2loc.c dwarf2loc.h > dwarf2cfi.c dwarf2cfi.h (consider these deprecated) > dwarf-frame.c dwarf-frame.h (on the i386newframe branch) > > The dwarfread.c module exports only one function: > dwarf_build_psymtabs(). The dwarf2*.c modules export several > functions, some with the dwarf2_ prefix, some with the dwarf_ prefix, > and some with no prefix at all. I think Andrew would like to see that > we use dwarf2 in the names of files implementing DWARF-2 things, and > the dwarf2_ prefix for public function names. Is that right? If > people agree, I'll rename my DWARF CFI bits before I move things over > to mainline. yes please, that would be super. thanks elena > > Mark