From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25469 invoked by alias); 23 Sep 2003 19:49:20 -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 25436 invoked from network); 23 Sep 2003 19:49:19 -0000 Received: from unknown (HELO localhost.redhat.com) (207.219.125.105) by sources.redhat.com with SMTP; 23 Sep 2003 19:49:19 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 8F1372B89; Tue, 23 Sep 2003 15:49:22 -0400 (EDT) Message-ID: <3F70A3C2.5080504@redhat.com> Date: Tue, 23 Sep 2003 19:49:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030820 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jim Blandy Cc: gdb-patches@sources.redhat.com Subject: Re: [6.0] PROBLEMS and NEWS References: <3F6CBFA5.7060308@redhat.com> <3F6F499E.7020102@redhat.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-09/txt/msg00504.txt.bz2 > Looks good, just some picky comments: > > Andrew Cagney writes: > >> +* New back-trace mechanism (includes DWARF 2 Call Frame Identification). >> + >> +DWARF 2's Call Frame Identification makes available compiler generated > > > s/Identification/Information/; that's what the spec calls it. Oops. >> +information that more exactly describes the program's run-time stack. >> +By using this information, GDB is able to provide more robust stack >> +back-traces. > > > The GDB manual uses "backtrace" throughout, never "back-trace". There > are other uses of "back-trace" in the proposed text. That will learn me for spellchecking it ... >> +* DWARF 2 Location Expressions >> + >> +DWARF 2 Location Expressions allow the compiler to more exactly >> +describe the location of variables to the debugger. > > > It'd be nice to give some indication of why the user would care about > this, like: "Taken together with Dwarf 2 Call Frame Information, > location expressions give GDB the information it needs to debug > optimized code much more effectively." At one stage I had the word optimized, but took it out. I've changed it to: DWARF 2 Location Expressions allow the compiler to more completly describe the location of variables (even in optimized code) to the debugger. IA64 ABI, for instance, specifies something other than CFI for doing unwinds so the LE <-> CFI link isn't that strong. Andrew