From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9191 invoked by alias); 12 Apr 2004 22:07:24 -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 9179 invoked from network); 12 Apr 2004 22:07:22 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sources.redhat.com with SMTP; 12 Apr 2004 22:07:22 -0000 Received: from drow by nevyn.them.org with local (Exim 4.31 #1 (Debian)) id 1BD9aF-0000Yd-U8; Mon, 12 Apr 2004 18:07:16 -0400 Date: Tue, 13 Apr 2004 14:15:00 -0000 From: Daniel Jacobowitz To: Andreas Schwab Cc: gdb@sources.redhat.com Subject: Re: DWARF location expressions considered harmful Message-ID: <20040412220715.GA2102@nevyn.them.org> Mail-Followup-To: Andreas Schwab , gdb@sources.redhat.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.5.1+cvs20040105i X-SW-Source: 2004-04/txt/msg00070.txt.bz2 On Mon, Apr 12, 2004 at 11:49:24PM +0200, Andreas Schwab wrote: > The introduction of DWARF location expressions has made debugging of > optimized code very difficult. Whenever a value is considered unavailable > by GDB the current operation is aborted immediately. This makes commands > like "info locals", "info args" or "info frame" pretty useless, because > there is no way to "skip" over those unavailable values to see the rest of > the information. That's because GDB support for location expressions is not in every way finished. You may want to file bugs with test cases. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer