From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23475 invoked by alias); 17 Apr 2006 09:05:00 -0000 Received: (qmail 23467 invoked by uid 22791); 17 Apr 2006 09:04:59 -0000 X-Spam-Check-By: sourceware.org Received: from zigzag.lvk.cs.msu.su (HELO zigzag.lvk.cs.msu.su) (158.250.17.23) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 17 Apr 2006 09:04:58 +0000 Received: from Debian-exim by zigzag.lvk.cs.msu.su with spam-scanned (Exim 4.50) id 1FVPf8-0000hk-41 for gdb@sources.redhat.com; Mon, 17 Apr 2006 13:04:55 +0400 Received: from zigzag.lvk.cs.msu.su ([158.250.17.23]) by zigzag.lvk.cs.msu.su with esmtp (Exim 4.50) id 1FVPed-0000cC-Eb; Mon, 17 Apr 2006 13:04:19 +0400 From: Vladimir Prus To: Mark Kettenis Subject: Re: -var-update and address changes Date: Mon, 17 Apr 2006 10:54:00 -0000 User-Agent: KMail/1.7.2 Cc: drow@false.org, jingham@apple.com, gdb@sources.redhat.com References: <200604170953.57667.ghost@cs.msu.su> <200604170840.k3H8ePll027359@elgar.sibelius.xs4all.nl> In-Reply-To: <200604170840.k3H8ePll027359@elgar.sibelius.xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200604171304.19041.ghost@cs.msu.su> Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-04/txt/msg00235.txt.bz2 On Monday 17 April 2006 12:40, Mark Kettenis wrote: > > And that PC is of some use too. I some distant future, I want to make > > KDevelop remember the state of variables tree for a specific frame. Say, > > you've entered function 'foo' and switched display format for variable > > 'mask' from 'natural' to 'binary'. You probably want binary format to be > > used whenever you enter 'foo' next time. Using frame PC is one way to > > capture the current frame. It's not ideal, since frame address can change > > on recompilation, but on the other hand, the worst thing that will happen > > is that you'll use wrong format for a variable, which is not big > > problems. > > > > So, I think frame PC is useful on it's own. > > Address space randomization (used by OpenBSD and any halfway decent > Linux distribution) will kill this idea completely. The frame ID will > vary from run to run on those systems. I know and would appreciate a more reliable mechanism (say, opaque "scope id"). Even with address randomization things will work if you enter the same function several times without restarting application. - Volodya