From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3567 invoked by alias); 19 Apr 2004 16:34:22 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 3550 invoked from network); 19 Apr 2004 16:34:22 -0000 Received: from unknown (HELO esds.vss.fsi.com) (66.136.174.212) by sources.redhat.com with SMTP; 19 Apr 2004 16:34:22 -0000 Received: from thing1.vss.fsi.com (thing1.vss.fsi.com [198.51.29.21]) by esds.vss.fsi.com (8.11.6+Sun/8.9.1) with ESMTP id i3JGYGd11412; Mon, 19 Apr 2004 11:34:16 -0500 (CDT) Received: from localhost (ford@localhost) by thing1.vss.fsi.com (8.11.6+Sun/8.11.6) with ESMTP id i3JGYGZ23815; Mon, 19 Apr 2004 11:34:16 -0500 (CDT) X-Authentication-Warning: thing1-200.fsi.com: ford owned process doing -bs Date: Mon, 19 Apr 2004 16:34:00 -0000 From: Brian Ford X-X-Sender: ford@thing1-200 To: Eli Zaretskii cc: gdb-patches@sources.redhat.com Subject: Re: ix86 PE/COFF DWARF register numbering In-Reply-To: Message-ID: References: <8011-Fri02Apr2004094123+0300-eliz@gnu.org> <2719-Fri02Apr2004213907+0300-eliz@gnu.org> <2914-Sun18Apr2004194339+0300-eliz@gnu.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2004-04/txt/msg00427.txt.bz2 On Mon, 19 Apr 2004, Eli Zaretskii wrote: > On Sun, 18 Apr 2004 at 21:06:37 -0500 (CDT) Brian Ford wrote: > > > And note that for DWARF 2, [DJGPP] uses the svr4 map, just like every > > other ix86 target I know of (except the current PE proposal). > > This was done at Mark Kettenis's suggestion, back in 2001, as you > will see in the thread I cited a few days ago. Yes, I saw that suggestion here: http://sources.redhat.com/ml/gdb/2001-07/msg00398.html and commented on it here: http://sources.redhat.com/ml/gdb/2001-07/msg00398.html > In the DJGPP project, we simply took that suggestion and implemented it > in GCC when DWARF-2 support for DJGPP was first added to GCC. but there was no follow-up that stated which of the two possible suggestions were chosen. Taking together FSF GCC sources and GDB sources showed the issue was still unresolved. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444