From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4634 invoked by alias); 1 Jul 2003 12:45:38 -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 4627 invoked from network); 1 Jul 2003 12:45:38 -0000 Received: from unknown (HELO crack.them.org) (146.82.138.56) by sources.redhat.com with SMTP; 1 Jul 2003 12:45:38 -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 19XKWp-0007ga-00 for ; Tue, 01 Jul 2003 07:46:35 -0500 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 19XKVr-0002R0-00 for ; Tue, 01 Jul 2003 08:45:35 -0400 Date: Tue, 01 Jul 2003 12:45:00 -0000 From: Daniel Jacobowitz To: gdb@sources.redhat.com Subject: Re: Frame handling Message-ID: <20030701124535.GA9334@nevyn.them.org> Mail-Followup-To: gdb@sources.redhat.com References: <00cd01c33f8d$b4e570e0$0a00a8c0@nkelseyhome> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <00cd01c33f8d$b4e570e0$0a00a8c0@nkelseyhome> User-Agent: Mutt/1.5.1i X-SW-Source: 2003-07/txt/msg00011.txt.bz2 On Mon, Jun 30, 2003 at 10:00:21PM -0700, Jafa wrote: > Out of interest, what is the theory behind the frame id being made up of > address + func? The theory is that the frame ID is persistent. It lives until the frame goes out of scope (locals with watchpoints on them disappear, frame-specific breakpoints, etc.). Stack addr isn't enough, because of frameless functions; but PC is too volatile. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer