From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26865 invoked by alias); 5 May 2004 18:30:06 -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 26856 invoked from network); 5 May 2004 18:30:05 -0000 Received: from unknown (HELO mail-out3.apple.com) (17.254.13.22) by sources.redhat.com with SMTP; 5 May 2004 18:30:05 -0000 Received: from mailgate1.apple.com (a17-128-100-225.apple.com [17.128.100.225]) by mail-out3.apple.com (8.12.11/8.12.11) with ESMTP id i45IUF6K011105 for ; Wed, 5 May 2004 11:30:15 -0700 (PDT) Received: from relay3.apple.com (relay3.apple.com) by mailgate1.apple.com (Content Technologies SMTPRS 4.3.6) with ESMTP id ; Wed, 5 May 2004 11:30:04 -0700 Received: from apple.com ([17.219.199.8]) by relay3.apple.com (8.12.11/8.12.11) with ESMTP id i45ITifF004777; Wed, 5 May 2004 11:29:47 -0700 (PDT) Message-ID: <409932A9.3040504@apple.com> Date: Wed, 05 May 2004 18:30:00 -0000 From: Stan Shebs User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.6) Gecko/20040113 MIME-Version: 1.0 To: Kean Johnston CC: Andrew Cagney , Michael Elizabeth Chastain , ezannoni@redhat.com, gdb@sources.redhat.com, jimb@redhat.com Subject: Re: Phasing out Dwarf 1? References: <20040505052310.A2AF64B104@berman.michael-chastain.com> <4098FAA6.9020306@gnu.org> <40990E80.4090906@sco.com> In-Reply-To: <40990E80.4090906@sco.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-05/txt/msg00035.txt.bz2 Kean Johnston wrote: >> If you installed operating system X, including the vendor compiler, >> and typed `cc -g ..` would the debug format be dwarf-1? >> >> Of those, how many do we still support. > > At least 3 I know of: SCO, UnixWare ans Solaris x86. DG-UX may as well, > but I cant swear to its native debugging format. I wish I could say > I will have the energy and time to maintain this in gdb but I just > cant say that. Id be far more interested in getting it doing correct > stack traces in 6.1 on SCO than in supporting DWARF1. This confuses me a bit - what debugging format would you use if Dwarf 1 were no longer available? Stan