From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1621 invoked by alias); 5 Jun 2003 03:46:58 -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 1500 invoked from network); 5 Jun 2003 03:46:57 -0000 Received: from unknown (HELO crack.them.org) (146.82.138.56) by sources.redhat.com with SMTP; 5 Jun 2003 03:46:57 -0000 Received: from dsl093-172-017.pit1.dsl.speakeasy.net ([66.93.172.17] helo=nevyn.them.org ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 19Nlj0-0003tW-00 for ; Wed, 04 Jun 2003 22:47:38 -0500 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 19NliH-0002Pa-00 for ; Wed, 04 Jun 2003 23:46:53 -0400 Date: Thu, 05 Jun 2003 03:46:00 -0000 From: Daniel Jacobowitz To: gdb@sources.redhat.com Subject: RFC: Backtrace vs. list in recent GDB Message-ID: <20030605034652.GA8918@nevyn.them.org> Mail-Followup-To: gdb@sources.redhat.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.1i X-SW-Source: 2003-06/txt/msg00063.txt.bz2 Sometime between GDB 5.2 and GDB 5.3, when the default-source-location code was touched, backtrace began changing the notion of the "current source location". As a result, if you say "backtrace" and then "list" now, you get the last listed frame's source location - not the previous default location. Personally, I think that's wrong. I don't think it was deliberate, but I might have missed something... any comments? It seems to me that this doesn't represent any more fundamental bug, but just that backtrace should save and restore the current source location. Does anyone else have an opinion, before I implement that? -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer