From: Tom Tromey <tom@tromey.com>
To: Hannes Domani <ssbssa@yahoo.de>
Cc: Tom Tromey <tom@tromey.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Fix casting in-memory values of primitive types to const reference
Date: Wed, 20 Mar 2024 11:33:40 -0600 [thread overview]
Message-ID: <875xxgg64r.fsf@tromey.com> (raw)
In-Reply-To: <745860198.11199509.1710955557445@mail.yahoo.com> (Hannes Domani's message of "Wed, 20 Mar 2024 17:25:57 +0000 (UTC)")
>>>>> "Hannes" == Hannes Domani <ssbssa@yahoo.de> writes:
Hannes> This happens:
Hannes> (gdb) p (ci&) Q.id
Hannes> $1 = (const int &) @0x3cfb8c: 42
Hannes> Because check_typedef is called when the reference is removed:
Thanks for looking.
Tom
prev parent reply other threads:[~2024-03-20 17:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240320160844.106-1-ssbssa.ref@yahoo.de>
2024-03-20 16:08 ` Hannes Domani
2024-03-20 17:05 ` Tom Tromey
2024-03-20 17:25 ` Hannes Domani
2024-03-20 17:33 ` Tom Tromey [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=875xxgg64r.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=ssbssa@yahoo.de \
/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).