From: Daniel Jacobowitz <drow@false.org>
To: Jim Blandy <jimb@codesourcery.com>
Cc: Douglas Evans <dje@google.com>,
Paul Hilfinger <Hilfinger@adacore.com>,
gdb@sourceware.org
Subject: Re: print/x on references
Date: Fri, 19 Oct 2007 22:00:00 -0000 [thread overview]
Message-ID: <20071019215953.GA27922@caradoc.them.org> (raw)
In-Reply-To: <m3r6jq941b.fsf@codesourcery.com>
On Fri, Oct 19, 2007 at 02:40:32PM -0700, Jim Blandy wrote:
> For debugging C++, GDB implements a use of `&' beyond what is
> allowed in the C++ language itself: you can use `&(&REF)' (or, if
> you prefer, simply `&&REF') to examine the address where a C++
> reference variable (declared with `&REF') is stored.
Good for us. Shame on us for having no test cases for it! I wonder
if &&REF really works.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2007-10-19 22:00 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
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 [this message]
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=20071019215953.GA27922@caradoc.them.org \
--to=drow@false.org \
--cc=Hilfinger@adacore.com \
--cc=dje@google.com \
--cc=gdb@sourceware.org \
--cc=jimb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).