Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <ghost@cs.msu.su>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: drow@false.org,  jingham@apple.com,  gdb@sources.redhat.com
Subject: Re: -var-update and address changes
Date: Mon, 17 Apr 2006 10:54:00 -0000	[thread overview]
Message-ID: <200604171304.19041.ghost@cs.msu.su> (raw)
In-Reply-To: <200604170840.k3H8ePll027359@elgar.sibelius.xs4all.nl>

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


  reply	other threads:[~2006-04-17  9:05 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-12 16:02 Vladimir Prus
2006-04-12 18:25 ` Jim Ingham
2006-04-13  9:25   ` Vladimir Prus
2006-04-13 17:31     ` Jim Ingham
2006-04-14 13:25   ` Daniel Jacobowitz
2006-04-14 20:03     ` Jim Ingham
2006-04-14 20:09       ` Daniel Jacobowitz
2006-04-14 20:27         ` Jim Ingham
2006-04-14 21:37           ` Daniel Jacobowitz
2006-04-17  6:18             ` Vladimir Prus
2006-04-17  9:02               ` Mark Kettenis
2006-04-17 10:54                 ` Vladimir Prus [this message]
2006-05-02 12:50       ` Vladimir Prus
2006-05-02 13:14         ` Nick Roberts
2006-05-02 13:41           ` Vladimir Prus
2006-05-02 17:23             ` Jim Ingham
2006-05-03  6:03               ` Vladimir Prus
     [not found]                 ` <20060504145046.GA32605@nevyn.them.org>
2006-05-04 15:12                   ` Vladimir Prus
2006-05-04 15:13                     ` Daniel Jacobowitz
2006-05-05  6:25                   ` Vladimir Prus
2006-05-05 15:02                     ` Daniel Jacobowitz
2006-04-16 15:52     ` Nick Roberts

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200604171304.19041.ghost@cs.msu.su \
    --to=ghost@cs.msu.su \
    --cc=drow@false.org \
    --cc=gdb@sources.redhat.com \
    --cc=jingham@apple.com \
    --cc=mark.kettenis@xs4all.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox