From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25210 invoked by alias); 17 May 2003 12:53:34 -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 25154 invoked from network); 17 May 2003 12:53:31 -0000 Received: from unknown (HELO walton.kettenis.dyndns.org) (62.163.169.212) by sources.redhat.com with SMTP; 17 May 2003 12:53:31 -0000 Received: from elgar.kettenis.dyndns.org (elgar.kettenis.dyndns.org [192.168.0.2]) by walton.kettenis.dyndns.org (8.12.6p2/8.12.5) with ESMTP id h4HCrUF3000440 for ; Sat, 17 May 2003 14:53:30 +0200 (CEST) (envelope-from kettenis@elgar.kettenis.dyndns.org) Received: from elgar.kettenis.dyndns.org (localhost [127.0.0.1]) by elgar.kettenis.dyndns.org (8.12.6p2/8.12.6) with ESMTP id h4HCrTs3012145 for ; Sat, 17 May 2003 14:53:30 +0200 (CEST) (envelope-from kettenis@elgar.kettenis.dyndns.org) Received: (from kettenis@localhost) by elgar.kettenis.dyndns.org (8.12.6p2/8.12.6/Submit) id h4HCrTT0012142; Sat, 17 May 2003 14:53:29 +0200 (CEST) Date: Sat, 17 May 2003 12:53:00 -0000 Message-Id: <200305171253.h4HCrTT0012142@elgar.kettenis.dyndns.org> From: Mark Kettenis To: gdb@sources.redhat.com Subject: [PATCH] Naming dwarves X-SW-Source: 2003-05/txt/msg00259.txt.bz2 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. Mark