From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7948 invoked by alias); 15 Jan 2003 19:47:49 -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 7927 invoked from network); 15 Jan 2003 19:47:46 -0000 Received: from unknown (HELO esds.vss.fsi.com) (66.136.174.212) by sources.redhat.com with SMTP; 15 Jan 2003 19:47:46 -0000 Received: from eos.vss.fsi.com (eos [198.51.27.61]) by esds.vss.fsi.com (8.9.1a/8.9.1) with ESMTP id NAA20943; Wed, 15 Jan 2003 13:47:44 -0600 (CST) Received: from localhost (ford@localhost) by eos.vss.fsi.com (8.11.6+Sun/8.11.6) with ESMTP id h0FJlhJ24330; Wed, 15 Jan 2003 13:47:43 -0600 (CST) X-Authentication-Warning: eos.vss.fsi.com: ford owned process doing -bs Date: Wed, 15 Jan 2003 19:47:00 -0000 From: Brian Ford X-X-Sender: ford@eos To: binutils@sources.redhat.com, , Subject: Non-zero VMA's w/DWARF-2? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2003-01/txt/msg00275.txt.bz2 I am trying to add DWARF-2 support to Cygwin. I have run into the problem that all example DWARF-2 implementations seem to expect the .debug_* sections' VMAs to be zero. This contradicts the PE/coff object format as I read it, and the resulting executable will not run. >From "Microsoft Portable Executable and Common Object File Format Specification 6.0": 4.) Section Table (Section Headers) In an image file, the virtual addresses for sections must be assigned by the linker such that they are in ascending order and adjacent, and they must be a multiple of the Section Align value in the optional header. and 5. Other Contents of the File The remainder of a COFF object or image file contains blocks of data that are not necessarily at any specific file offset. Instead the locations are defined by pointers in the Optional Header or a section header. [...] Another exception is that attribute certificate and debug information must be placed at the very end of an image file (with the attribute certificate table immediately preceding the debug section), because the loader does not map these into memory. The rule on attribute certificate and debug information does not apply to object files, however. Am I reading this wrong? Who's the PE expert? Is there any hope of non-zero VMAs for .debug_* sections? Thanks. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444