Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sources.redhat.com, Nick Roberts <nickrob@snap.net.nz>
Subject: Re: MI/C++/references fixup
Date: Wed, 29 Nov 2006 14:24:00 -0000	[thread overview]
Message-ID: <20061129142435.GD29365@nevyn.them.org> (raw)
In-Reply-To: <200611291715.05247.vladimir@codesourcery.com>

On Wed, Nov 29, 2006 at 05:15:04PM +0300, Vladimir Prus wrote:
> > > +  /* We are not interested in address of references, and given
> > > +     that in C++ reference is not rebindable, it cannot
> > > +     meaningfully change.  So, get hold of the real value.  */
> >
> > in the address of a reference, in C++ a reference.
> >
> > In C++ it can't meaningfully change.  In a program, though, it can;
> > once when it's initialized, and again if something scribbles on the
> > stack.  And that might be what you're trying to debug.  So, I'm
> > a little wary of this; it seems to me that we ought to check for both
> > changes in the address and value (sort of like we do for watchpoints).
> 
> In practice, if the address changes, the value also changes, so the user can 
> notice. Second, if user really wants to get the address, he can do that 
> with "&whatever".

I suppose that's true.  Want to post an updated patch, and we'll see if
anyone has a reason to keep it?  We're leaving the CLI as it was, this
time.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-11-29 14:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-29  9:15 Vladimir Prus
2006-11-29  9:25 ` Vladimir Prus
2006-11-29 14:01 ` Daniel Jacobowitz
2006-11-29 14:15   ` Vladimir Prus
2006-11-29 14:24     ` Daniel Jacobowitz [this message]
2006-11-29 14:41       ` Vladimir Prus
2006-11-29 23:59         ` Nick Roberts
2006-11-30  7:31           ` Vladimir Prus
2006-12-05 21:11       ` Daniel Jacobowitz
2006-12-06  9:17         ` Vladimir Prus
2006-12-07 14:39           ` Daniel Jacobowitz
2006-12-08 12:45             ` Vladimir Prus

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=20061129142435.GD29365@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=nickrob@snap.net.nz \
    --cc=vladimir@codesourcery.com \
    /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