public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Douglas Evans <dje@google.com>
Cc: Paul Hilfinger <Hilfinger@adacore.com>, gdb@sourceware.org
Subject: Re: print/x on references
Date: Thu, 18 Oct 2007 17:11:00 -0000	[thread overview]
Message-ID: <20071018171114.GA21738@caradoc.them.org> (raw)
In-Reply-To: <e394668d0710181003j836bd06jc4cb50affb28e061@mail.gmail.com>

On Thu, Oct 18, 2007 at 10:03:01AM -0700, Douglas Evans wrote:
> On 10/18/07, Daniel Jacobowitz <drow@false.org> wrote:
> > On Thu, Oct 18, 2007 at 09:04:48AM -0700, Douglas Evans wrote:
> > > (gdb) p/x x -> prints same as $4 but in hex
> > > (gdb) p &x -> prints pointer (e.g. "$5 = (Glorp *) 0x8049850")
> > >
> > > $0.02
> >
> > And then there's no way to find the address of the reference?
> 
> To find the address of the pointer to the object I was thinking "p
> &(&x)".  It works, at least in the simple example I used to experiment
> with.

That is such a horrible abuse of C++ that I didn't even think to try
it.  Egads.  Not quite sure how I feel about that!

-- 
Daniel Jacobowitz
CodeSourcery

  parent reply	other threads:[~2007-10-18 17:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-18  9:37 Paul Hilfinger
2007-10-18 11:16 ` Daniel Jacobowitz
2007-10-18 16:05   ` Douglas Evans
2007-10-18 16:30     ` Daniel Jacobowitz
2007-10-18 17:03       ` Douglas Evans
2007-10-18 17:10         ` Douglas Evans
2007-10-18 17:11         ` Daniel Jacobowitz [this message]
2007-10-18 17:45           ` Douglas Evans
2007-10-18 19:10             ` Paul Hilfinger
2007-10-18 19:21             ` Daniel Jacobowitz
2007-10-18 19:30               ` Paul Hilfinger
2007-10-18 19:39                 ` Daniel Jacobowitz
2007-10-19 21:40               ` Jim Blandy
2007-10-19 22:00                 ` Daniel Jacobowitz

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=20071018171114.GA21738@caradoc.them.org \
    --to=drow@false.org \
    --cc=Hilfinger@adacore.com \
    --cc=dje@google.com \
    --cc=gdb@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).