From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12716 invoked by alias); 6 Oct 2003 14:49:45 -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 12690 invoked from network); 6 Oct 2003 14:49:44 -0000 Received: from unknown (HELO dberlin.org) (69.3.5.6) by sources.redhat.com with SMTP; 6 Oct 2003 14:49:44 -0000 Received: from [192.168.1.7] (account dberlin [192.168.1.7] verified) by dberlin.org (CommuniGate Pro SMTP 4.1.4) with ESMTP-TLS id 5120906; Mon, 06 Oct 2003 10:49:41 -0400 In-Reply-To: <20031006134604.GA31005@nevyn.them.org> References: <20031001144330.GA11707@artax.karlin.mff.cuni.cz> <20031001144937.GA4613@nevyn.them.org> <20031001154415.GA15387@artax.karlin.mff.cuni.cz> <20031001155417.GA13942@nevyn.them.org> <20031001160318.GA17042@artax.karlin.mff.cuni.cz> <20031001162255.GA25428@nevyn.them.org> <20031001174142.GA21499@artax.karlin.mff.cuni.cz> <20031001174427.GA13387@nevyn.them.org> <20031006062216.GB26462@redhat.com> <20031006064016.GA13046@artax.karlin.mff.cuni.cz> <20031006134604.GA31005@nevyn.them.org> Mime-Version: 1.0 (Apple Message framework v606) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <1BEF617C-F80C-11D7-8E4F-000A95AF1FAE@dberlin.org> Content-Transfer-Encoding: 7bit Cc: Richard Henderson , gdb@sources.redhat.com, Josef Zlomek From: Daniel Berlin Subject: Re: Problem with location lists and variables on stack Date: Mon, 06 Oct 2003 14:49:00 -0000 To: Daniel Jacobowitz X-SW-Source: 2003-10/txt/msg00097.txt.bz2 >> Daniel Berlin has already written support for GCC to generate location >> list for DW_AT_frame_base. >> DW_AT_frame_base is a location list as any other (actually only the >> offsets relatively to original stack pointer at function start are >> needed). >> GDB then uses this location list to adjust offsets of other variables >> addressed using stack pointer. >> With Daniel Jacobowitz's fix for GDB it works :-) >> i.e. you can see correct values for variables located on stack >> even when stack pointer changes because of push, pop, etc. >> >> Current GCC patch can be downloaded from: >> http://artax.karlin.mff.cuni.cz/~zlomj9am/download/vt-main.patch >> >> (because currently GCC is in stage 2 it has to wait until GCC is in >> stage 1) > > I suppose this is true, but it's really unfortunate. I'm not so sure it's true. This isn't a major change, really and it's only going to make things better (We didn't use to support -O2 -g at all, really, and now we can. There can't be any regressions from an unsupported state to a supported one). It's also not an optimization pass, so the risk is relatively low. > > -- > Daniel Jacobowitz > MontaVista Software Debian GNU/Linux Developer